Bug 1480793
| Summary: | ecryptfs-mount-private fails to mount if passphrase is not on root's keyring | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andre Costa <andre.ocosta> |
| Component: | ecryptfs-utils | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | csdietz123, esandeen, mhlavink, projects.rg, ray, sebp |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-07-19 21:32:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Andre Costa
2017-08-11 21:53:34 UTC
Filed bug #1480795 Do you have something "different" on your machine? I'm not able to reproduce this. Fresh new virtual machine with Fedora 26, new user "qemuser", added to group ecryptfs [qemuser@f26 ~]$ ecryptfs-setup-private --no-fnek --noautomount Enter your login passphrase [qemuser]: Enter your mount passphrase [leave blank to generate one]: ************************************************************************ YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION. ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME. ************************************************************************ INFO: /home/qemuser/Private will not be mounted on login /usr/sbin/restorecon /usr/sbin/restorecon Done configuring. Testing mount/write/umount/read... Inserted auth tok with sig [ad1cef28d3a3ba22] into the user session keyring Inserted auth tok with sig [ad1cef28d3a3ba22] into the user session keyring Testing succeeded. Logout, and log back in to begin using your encrypted directory. [qemuser@f26 ~]$ ecryptfs-mount-private Enter your login passphrase: Inserted auth tok with sig [ad1cef28d3a3ba22] into the user session keyring [qemuser@f26 ~]$ mount | grep ecryptfs /home/qemuser/.Private on /home/qemuser/Private type ecryptfs (rw,nosuid,nodev,relatime,ecryptfs_sig=ad1cef28d3a3ba22,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs) Even SElinux is enabled in enforcing mode. ------ I CAN reproduce this, when I become qemuser from root with "su qemuser", in that case it will fail the same way as you've described. But it's to be expected, as after "su qemuser" environment was not (re)set correctly for qemuser and you are still partially original user (root in this case). As far as I am concerned, there is nothing different with this machine -- but there could be something different with my user. I also tried creating a new user on my machine, and did the same process of creating ~/.Private for him. To my surprise, it worked out of the box. The only difference I can see is that my user has sudo rights (it has been created as a "Administrator"), while this test user I created was a regular account. The upgrade to F26 has followed the same procedure I've been using for quite some time already: I preserve /home (which is on a separate partition), and reformat / and swap. I'm using ext4 on LVM. What kind of info can I provide you to help you narrow down the cause of the problem? Any SELinux data? LVM? I'm experiencing the same problem. It seems to be related to an issue in systemd: https://github.com/systemd/systemd/pull/6286 (via https://bugs.archlinux.org/task/54670). The fix from the systemd issue above (https://github.com/systemd/systemd/pull/6342) can be applied manually by manually linking the user and session keyring via keyctl link @u @s before running ecryptfs-mount-private This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Maybe dup of bug #1538760? Reporter, can you still reproduce in a current branch? No response so far from reporter. Closing again. |