Beleriand [2008-11-27 9:01 -]:
> That's what I thought, too. And for that reason I think it's a feature
> not to mount the encrypted directory on login and not a bug.
It *can't* be a bug. If it would be possible to unlock the encrypted
directory fully automatically, then you don't need to enc
Beleriand [2008-11-26 19:51 -]:
> I have a question: Does it make any sense to have an encrypted directory
> and auto-login as well?
Sure, if you are fine with unlocking it manually. E. g. you might
store documents there which you don't always need.
However, I use it to store my ssh/gpg keys
People complained about the Private directory showing up on the
desktop and it was removed in a separate patch to Gnome somewhere (not
in ecryptfs-utils).
:-Dustin
--
Cannot open Private directory after a reboot when "Automatic Login" enabled
https://bugs.launchpad.net/bugs/259631
You received t
am28111-
* The "salt value" messages are merely warnings, and are benign, and
will not cause a problem.
* The "ecryptfs_insert_wrapped_passphrase_into_keyring" bit was a
typo on my part. Replace the underscores with hyphens.
* If you're getting "Error attempting to unwrap passphrase", then you
Jim-
I have posted instructions at:
* https://help.ubuntu.com/community/EncryptedPrivateDirectory
As to how to add links to your unmounted Private directory, that would
allow you to double click on "Access Your Private Data" link, enter
your password, and then mount your private directory.
:-Du
Jim, please note that the fix in this bug, to get a "clickable"
unencryption, only applies to newly created private directories.
Also, this feature isn't really pointless IMHO, it works very well for
people without autlogin. With this fix it works reasonably well for
autologins as well, it's just
Documented manually adding the symlinks to a legacy-installed
encrypted private directory here:
https://help.ubuntu.com/community/EncryptedPrivateDirectory
:-Dustin
--
Cannot open Private directory after a reboot when "Automatic Login" enabled
https://bugs.launchpad.net/bugs/259631
You received
One update to my last post... That hack might actually have to go
into pam_ecryptfs.so.
:-Dustin
--
Cannot open Private directory after a reboot when "Automatic Login" enabled
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Martin-
The fix, as proposed, will only solve this comprehensively for *newly*
created encrypted-private setups, with the patched
ecryptfs-setup-private.
I didn't think it appropriate for upgrading the package to go digging
in user's unmounted ~/Private directory, creating symlinks to the
readme.
ubuntostones-
Aha! Thanks for the excellent detective work.
Absolutely, automatic mounting of encrypted ~/Private cannot work with
automatic logins.
Mounting of encrypted ~/Private requires you to enter your password at
login. If you have not done so, the required key is not present, and
thus
Okay, it's my best guess at this point that you're suffering from some
weird perturbation of Bug #290445.
The fix for that bug should land in intrepid-updates within a day or
two.
If you'd like to try it now, though, you can try
ecryptfs-utils_53-1ubuntu12~ppa1 in my PPA:
* https://edge.launchpa
Rob,
Might your problem be related to Bug #290445, having any strange
characters in your passphrase? Please don't reveal your passphrase,
but there is a known bug (with a fix coming)...
:-Dustin
--
Cannot open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received
Rob-
Reboot.
Login.
Run: "keyctl show". This should show the signature of the key used
(not the key itself. Does that signature matches the value in
~/.ecryptfs/Private.sig?
If that key signature is missing, or two two do not match, that's
where we need to start debugging this problem.
:-Du
Rob-
Do you have any cronjobs running as your normal user, or as root?
$ crontab -l
$ sudo crontab -l
$ ls -alF /etc/cron*
:-Dustin
--
Cannot open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you are a member of Ubuntu
Bu
Steve-
Any ideas about an arbitrary delay of roughly 5 minutes that PAM might
somehow introduce?
Rune-
Do you have any cronjobs running?
:-Dustin
--
Cannot open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you are a member
On Tue, Oct 21, 2008 at 10:53 AM, Rune Evjen <[EMAIL PROTECTED]> wrote:
> In any case, is it possible to take the mount_passphrase and reverse it in
> order to compare it to the original login_passphrase ? Or can one
> mount_passphrase be generated from different login passwords ?
The mount_passph
> 2. I put in the wrong password, but it succeeded anyway
You entered the "wrong" login passphrase twice?
:-Dustin
--
Cannot 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 subscrib
Thank you for your response, I will test this shortly.
Please not that the output I posted is not the complete output of the unwrap
command.
In any case, is it possible to take the mount_passphrase and reverse it in
order to compare it to the original login_passphrase ? Or can one
mount_passphras
18 matches
Mail list logo
