Dustin,
ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase [LOGIN_PASSPHRASE]
(with my actual login password) returns
Unable to read salt value from user's .ecryptfsrc file; using default
fa0ec2d..
Clicking the link in ~/Private after this does not mount the directory,
and the
Did you run ecryptfs-setup-private from the command line, or did you
choose to have an encrypted private directory in the installer?
When you run 'ecryptfs-unwrap-passphrase', after the warning about the
salt value, does it return your mount passphrase? What's the exit code?
(Hint: echo $?)
Same problem here, even after deleting .ecryptfs .Private and Private folders.
After reboot, Private is not automounted.
Doubleclicking on that long softlink found in Private doesnt do anything.
Executing mount.ecryptfs_private in terminal returns: required key not found.
Executing
The bug Can't open Private Directory after reboot affects me as well.
I am positive that I have the same passphrase as my login password, and get the
same error message
keyctl_search: Required key not available
Rune
--
Can open Private directory after a reboot
Please attempt to run:
$ ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase [LOGIN_PASSPHRASE]
And see if that utility is able to unwrap your mount passphrase.
:-Dustin
--
Can open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this bug
Change that to Can't open Private directory after reboot.
I must of had my stupid hat on yesterday, as I can't duplicate the
problem I was having with being able to open private directories system
wide.
Please mark this bug solved
Jim
--
Can open Private directory after a reboot
Thanks!!!
** Changed in: ecryptfs-utils (Ubuntu)
Status: New = Invalid
--
Can open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Yes, I did use my login password, I've used the force option three times
using the same login password and I still get the same error on reboot.
--
Can open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you are a member of
I created a new user and set up the private directory and it worked as
the way it should, so I went into my home directory and deleted .Private
and .ecryptfs and set up a private directory and it now works correctly.
I now have run into another problem. Before leaving my home directory I
umounted
Hello, thanks for reporting bugs to Ubuntu.
Please forgive me, I'm a little baffled on this bug report...
First, please correct the title/description, as I don't think:
Can open Private directory after a reboot
is what you mean as the topic of this bug.
Second, if that bug is solved, let's
10 matches
Mail list logo
