Skip to content
This repository has been archived by the owner. It is now read-only.

Detect errors caused by eCryptFS #61

Closed
lawl opened this issue Jun 4, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@lawl
Copy link
Contributor

commented Jun 4, 2017

eCryptFS seems to make a bunch of trouble, eg. #53 #51 #9 basically it doesn't behave like a regular filesystem.

Proposal: Detect eCryptFS and spit out a warning that this filesystem (in userspace) is unsupported.

@ollieparanoid

This comment has been minimized.

Copy link
Member

commented Jun 4, 2017

as I wrote in #53:

If we do implement a check, it should really check if /dev/random etc. work after creating them, instead of assuming, that if the filename length is limited, it must be ecryptfs (reminds me of these bad browser checks: if you can't do that, you must be browser xy).

@lawl

This comment has been minimized.

Copy link
Contributor Author

commented Jun 4, 2017

That makes sense. Closing this then.

@lawl lawl closed this Jun 4, 2017

@lawl

This comment has been minimized.

Copy link
Contributor Author

commented Jun 5, 2017

Actually, how do we want to proceed here.

@lawl lawl reopened this Jun 5, 2017

@ollieparanoid

This comment has been minimized.

Copy link
Member

commented Jun 5, 2017

My suggestion would be checking if /dev/random etc. work after they have been created. If they do not, raise a meaningful exception, that also mentions eCryptFS.

@ollieparanoid ollieparanoid changed the title eCryptFS Detect errors caused by eCryptFS Jun 5, 2017

PureTryOut added a commit that referenced this issue Feb 21, 2018

Fix #61: Check whether device nodes exist, after they have been created.
As reported in #53, it appears that older versions of eCryptfs don't
really create the device nodes, although `mknod` does not fail on
the commandline. That's fixed now with this extra check.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.