[dm-crypt] crypttab "tmp" option and /tmp 1777 permissions

Andrey Borzenkov arvidjaar at gmail.com
Sun Feb 9 06:41:56 CET 2014


Interesting thread
https://forums.opensuse.org/showthread.php/495266-After-update-root-works-but-not-regular-user which boils down to following:

user is using "tmp" option for /tmp crypto container in /etc/crypttab
(in this case it seems it was created by installer without user even
realizing it). This recreates filesystem every time, this resetting
permissions of fs root to default. It in turn breaks KDM which
needs /tmp to be writable.

I wonder what is the proper place to fix it. Reading crypttab manual,
it says

           The encrypted block device will be prepared for using it as /tmp;
           it will be formatted using mke2fs(8). This option implies plain.

And /tmp is almost universally used with 1777 permissions today (and it
is expected to be world writable in any case), so I would say -
cryptsetup should do it; the only question is whether it should do it
unconditionally?


More information about the dm-crypt mailing list