improve ecryptfs-mount-private output at error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When ecryptfs-
Steps to reproduce:
<code>
# Open system recovery and open root console
remount -o remount,rw /
init 3
su <user>
ecryptfs-
# enter login password
</code>
This will print
<output>
inserted auth tok with sig [...] into the user session keyring
open: No such file or directory
Error locking counter
</output>
user doesn't have any idea what went wrong, but output could be helpful, e.g. tell WHICH file or directory is missing.
version information depend on:
https:/
Changed in ecryptfs: | |
status: | New → Confirmed |
Should anybody trying to be mount an encrypted volume in 2017 from a recovery root prompt, the following steps work on Ubuntu 14.
The primary missing file is the symlink of `/dev/shm` to `/run/shm` and the permissions on the target when booted in this state.
export user="me" ecryptfs- mount-private
chgrp ${user} /run/shm
chmod g+w /run/shm
cd /dev
ln -s /run/shm/ shm
mount -o remount,rw $(mount | grep "on / type" | awk '{print $1}') /
su - ${user}
/usr/bin/