From: Heiko Rosemann <heiko.rosemann@web.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] crypttab "tmp" option and /tmp 1777 permissions
Date: Sun, 09 Feb 2014 11:46:36 +0100 [thread overview]
Message-ID: <52F75C8C.6050702@web.de> (raw)
In-Reply-To: <20140209094156.17061eb4@opensuse.site>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/09/2014 06:41 AM, Andrey Borzenkov wrote:
> 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 [...]
Cryptsetup/dm-crypt is not responsible for reading /etc/crypttab,
creating the filesystem and/or adjusting the permissions. This is left
to the distro maintainers (or maybe that know-it-all systemd - my
Slackware box has neither an /etc/crypttab nor systemd).
Even more so if the mapping is configured by the installer.
Best Regards,
Heiko
- --
eMails verschlüsseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlL3XIgACgkQ/Vb5NagElAWruQCfc8kylSzBxHTIYd2fClLdbFPt
w/MAn0fiCAjY9MIn8w7kOB1I2dCKVvdu
=Tq9o
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-02-09 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 5:41 [dm-crypt] crypttab "tmp" option and /tmp 1777 permissions Andrey Borzenkov
2014-02-09 10:46 ` Heiko Rosemann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F75C8C.6050702@web.de \
--to=heiko.rosemann@web.de \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox