** Tags added: verification-done
** Tags removed: verification-needed
--
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, which is subscribed to Ubuntu.
This bug was fixed in the package ecryptfs-utils - 53-1ubuntu13
---
ecryptfs-utils (53-1ubuntu13) intrepid-proposed; urgency=low
Fixes for LP: #259631, add interactive mounting capability
* debian/rules, debian/ecryptfs-utils.dirs,
debian/ecryptfs-utils.install, debian/ecryptf
I have tested with two accounts, one old and one newly created.
The old account works fine when I login with password. Also manually umounting
and mounting Private works fine. However, this account was apparently created
before this bug was fixed, so automatic login is hit by comment 60 and 61.
Anyone who can test this and at least confirm that it does not cause any
regressions?
--
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, which is subscrib
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
At least on autologin.
--
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, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
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.
--
Cannot open Private directory after a reboot when "Automatic Login" enabled
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you
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
Hi,
I have a question: Does it make any sense to have an encrypted directory
and auto-login as well?
Beleriand
--
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 Ubu
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
Dustin-
Thanks for the reply. Unfortunately, I could not figure out what the login
passphrase was so I just uninstalled the whole thing using the instructions at:
https://help.ubuntu.com/community/EncryptedPrivateDirectory
I then reinstalled it, but for some reason, I still can't get the
Priva
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
I still an unable to mount the private directory. When I run
'ecryptfs_insert_wrapped_passphrase_into_keyring ~/.ecryptfs/wrapped-passphrase
PASSPHRASE' it tells me the command is not found, changing it to
'ecryptfs-insert-wrapped-passphrase-into-keyring ~/.ecryptfs/wrapped-passphrase
PASSPHRAS
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
I have the same problem.
My install was an 8.04 and I did an upgrade to 8.10. I had it set up
under 8.04 to automatically log me in.
I had some success but it isn't persistent. Also the following command:
ecryptfs_insert_wrapped_passphrase_into_keyring ~/.ecryptfs/wrapped-
passphrase LOGIN_PAS
This bug was fixed in the package ecryptfs-utils - 66-2ubuntu1
---
ecryptfs-utils (66-2ubuntu1) jaunty; urgency=low
* Merge from debian unstable,
(LP: #259631, #293433, #286265, #247421, #294888, #298421)
* Remaining changes:
- debian/ecryptfs-utils.postinst: handle pam-au
** Changed in: ecryptfs
Status: Fix Committed => Fix Released
--
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, which is subscribed to Ubuntu.
--
The fix doesn't seem to work for me, i.e. I can't mount when I login
from SSH using public key auth. Also, I followed the instructions posted
above to create the symlinks in my unmounted Private directory, but the
files those symlinks should point to aren't there on my system.
For reference:
[EMA
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
Oh, thanks for the explanation, I wasn't aware that those files were
there only for newly encrypted ones. No, let's not touch user's ~ on
upgrade, that's fine.
--
Cannot open Private directory after a reboot when "Automatic Login" enabled
https://bugs.launchpad.net/bugs/259631
You received this b
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.
I activated auto-login, rebooted, and as expected ended up with
~/Private being unmounted. It had one file in it:
lrwxrwxrwx 1 martin martin 28 2008-10-28 16:54 THIS DIRECTORY HAS BEEN
UNMOUNTED TO PROTECT YOUR DATA -- Run mount.ecryptfs_private to mount
again -> /sbin/mount.ecryptfs_private
T
This -proposed fix worked for me. Be advised that I did not test SSH
though. Regards...
--
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, which is subs
** Changed in: ecryptfs-utils (Ubuntu)
Status: In Progress => Fix Committed
--
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, which is subscribed
Judging by the comments in #48 above, I suspect my problem is related.
I can log in to my test machine at the keyboard, and the ~/Private
directory is properly mounted. SSH in using public keys
(authorized_keys), and it is not mounted.
[EMAIL PROTECTED]:~$ /sbin/mount.ecryptfs_private
keyctl_sear
Accepted into intrepid-proposed, please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: ecryptfs-utils (Ubuntu Intrepid)
Status: In Progress => Fix Committed
** Ta
Thanks! I fixed the upload target to "intrepid-proposed" and uploaded.
I'll accept it once the previous SRU (bug #290445) is verified and moves
to -updates.
** Changed in: ecryptfs-utils (Ubuntu Intrepid)
Status: New => In Progress
--
Cannot open Private directory after a reboot when "Aut
Patch updated to remove 3 lines of non-functional shell code in the new
ecryptfs-mount-private script.
:-Dustin
** Attachment added: "ecryptfs-utils.259631.debdiff"
http://launchpadlibrarian.net/19343367/ecryptfs-utils.259631.debdiff
--
Cannot open Private directory after a reboot when "Auto
Stable Release Update Request
Per:
* https://wiki.ubuntu.com/StableReleaseUpdates
1) This bug affects any users using Intrepid's easy-to-configure
"Automatic Login" option, in conjunction with Encrypted Private
Directories. Encrypted Private Directories absolutely *require* that
you enter your
Updated patch attached, per Martin's comments.
Upstream commit:
*
http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=commit;h=168fab4991929b89220d006fe4b2df007871ba8a
:-Dustin
** Attachment added: "ecryptfs-utils.259631.debdiff"
http://launchpadlibrarian.net/19342073/ec
Dustin,
thanks a lot for working on this. I read the upstream commit, and it is
a great improvement to the current situation. Using a Terminal is okay
for now, since there are no cross-distro tools for DE agnostic password
input. Using gksu if it exists would be a nice improvement, of course. I
re
Fix committed to upstream git repository:
*
http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=commit;h=923a2e4bc05e8a6bb4a3ca836f9080b13bd84b3c
Will be released in version 64.
:-Dustin
** Changed in: ecryptfs
Status: In Progress => Fix Committed
--
Cannot open P
I'm attaching a debdiff that fixes this for Intrepid, and request that
this be sponsored for intrepid-proposed. I'll do the SRU momentarily.
:-Dustin
** Also affects: ecryptfs
Importance: Undecided
Status: New
** Changed in: ecryptfs
Importance: Undecided => Medium
Assignee: (
Okay, I have confirmed this bug, when a system is set to "automatically
login". I'm going to update the title of the bug accordingly.
:-Dustin
** Changed in: ecryptfs-utils (Ubuntu)
Status: Invalid => Confirmed
** Summary changed:
- Cannot open Private directory after a reboot
+ Cannot
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
Based on above bug descriptions, I figured it might have to do with the
new "automatic login" feature in 8.10. So I clean installed 8.10 final,
enabled "automatic login" through the graphical installer, and followed
the steps required to get the Private directory working. To little
surprise, I can
I think it's fixed. I had X automatically log me in because I was having
X issues a few weeks ago. So, remote reboots, no login, etc, etc.
Anyway, it seems that once I put in the password, it's all good.
--
Cannot open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You re
At some point over the last couple of hours, it worked. When I got up
this morning, it wasn't mounted. When I logged in from work, it was
mounted and the keyctl show and cat show the same thing now. So, I'm
thinking that that bug is not affecting me?
--
Cannot open Private directory after a reboo
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
My passphrase has an "!" in it...
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
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
$ keyctl show
Session Keyring
-3 --alswrv 1000-1 keyring: _uid_ses.1000
404603209 --alswrv 1000-1 \_ keyring: _uid.1000
$ cat ~/.ecryptfs/Private.sig
[removed]
Not the same... I recall doing this before and they did match (see
earlier in this thread).
--
Cannot open Private
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
Well, it still won't mound, I still get:
$ mount.ecryptfs_private
keyctl_search: Required key not available
--
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 subscribed to Ubu
10 minutes into a reboot, same deal, can't mount it.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
No idea why you would have a five-minute delay; anything loaded from
pam's session modules should happen synchronously within gdm before
login, TTBOMK.
cron was my first guess as well, but the evidence doesn't seem to point
that way?
--
Cannot open Private directory after a reboot
https://bugs.l
No.
[EMAIL PROTECTED]:~$ crontab -l
no crontab for rth
[EMAIL PROTECTED]:~$ sudo crontab -l
[sudo] password for rth:
no crontab for root
[EMAIL PROTECTED]:~$ ls -alF /etc/cron*
-rw-r--r-- 1 root root 724 2008-04-08 14:13 /etc/crontab
/etc/cron.d:
total 32
drwxr-xr-x 2 root root 4096 2008-10-
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
But it's RO. I can't write to it...
drwx-- 2 rth rth4096 2008-10-21 11:04 Private
drwx-- 2 rth rth4096 2008-10-21 11:04 .Private
That should mean that I can write to it.
--
Cannot open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this
Odd, now it mounted. I rebooted around 9:30 AM, it's not 1:22 PM and it
mounts.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailin
Now it's been a few hours since my last reboot (patches this AM) and it
won't mount at all.
--
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 subscribed to Ubuntu.
--
ubuntu
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
Dustin, here's the output of the grep command:
/etc/pam.d/common-auth:auth optionalpam_ecryptfs.so unwrap
/etc/pam.d/common-password:password optionalpam_ecryptfs.so
/etc/pam.d/common-session:session optionalpam_ecryptfs.so unwrap
I'm still at the point where
I'll try to add something to Launchpad Questions/Answers for ecryptfs,
since it seems a few users have experienced and solved this entirely as
a configuration problem.
Thanks,
:-Dustin
** Changed in: ecryptfs-utils (Ubuntu)
Status: Incomplete => Invalid
--
Cannot open Private directory a
Steve,
I ran 'sudo pam-auth-update --force' and checked both "eCryptfs
Key/Mount Management" and "ConsoleKit Session Management" which were
unchecked.
After rebooting my laptop the ~/Private directory automounted.
It was not intentional to keep an old pam.d configuration.
I was already using e
Rob H-
Can you check as well?
$ grep pam_ecryptfs /etc/pam.d/*
:-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 subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Hi Rune,
You appear not to be using the system-managed /etc/pam.d/common-* files
provided by pam-auth-update in Ubuntu 8.10. Is this intentional?
If you run 'sudo pam-auth-update --force', you can turn these files over
to the system for automatic management. I don't see anything unusual in
your
It works for me now. Not sure what came through with the last set of
updates today. I saw kernel and video driver updates, plus a bunch of
others. I wasn't looking to hard to see if there was anything with PAM.
--
Cannot open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
** Attachment added: "common-session"
http://launchpadlibrarian.net/18812515/common-session
--
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 subscribed to Ubuntu.
--
ub
** Attachment added: "common-password"
http://launchpadlibrarian.net/18812512/common-password
--
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 subscribed to Ubuntu.
--
Dustin,
Attached are the pam.d files.
'dpkg -l | grep ecryptfs':
ii ecryptfs-utils 53-1ubuntu10
ecryptfs cryptographic filesystem (utilities
ii libecryptfs0 53-1ubuntu10
ecryptf
I take that back. It seemed to work upon a couple previous reboots. Now when I
reboot, I try to mount it and I get the old message back:
keyctl_search: Required key not available
Last time I rebooted, I waited a minute and then tried again and it
mounted. Weird... This time I had to wait about 5
Rune-
Cool, thanks for the details. Multiple keys in the keyring should be
fine. The file ~/.ecryptfs/Private.sig tells mount.ecryptfs_private
which key should be used.
It sounds like your PAM configuration isn't correct.
Could you please post /etc/pam.d/common-session, /etc/pam.d/common-auth,
Test Result
1. First, you need to figure out if you can decrypt your
mount_passphrase, using 'ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-
passphrase LOGIN_PASSPHRASE'.
Result: Received salt warning, command printed the hex digits and
returned 0
2. Once you're able to successfully decrypt ~/.
Yes, I didn't realize that it was asking for my login password;
temporary brain cramp. I can type my password twice though... :)
So, I put in a different password, thinking it was for mounting the
encrypted folder. Then I put it in a 2nd time to confirm. Then it asked
for another password, I put i
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
Rune-
That "fa5c" value is your *mount* passphrase, which you have just
published to the internet. Consider any data there compromised.
Guys-
There are 2 passphrases involved.
1) There's your login_passphrase (what you use to login to the system)
2) And there's your mount_passphrase (wh
I seem to have the same problem. Here's what I did:
1. I ran ecryptfs-setup-private
2. I put in the wrong password, but it succeeded anyway
3. I tried to rerun ecryptfs-setup-private with the --force switch, it wouldn't
work
4. There was a PAM update that I saw go through yesterday? Not sure if it
I have been running Intrepid since alpha3, and installed it using the
command line instructions in the release notes. I did however already
have ecryptfs as I already used it in a more manual way. (adding the
passphrase=login password using ecyprfs-manager).
When running 'ecryptfs-unwrap-passphras
** Summary changed:
- Can open Private directory after a reboot
+ Cannot open Private directory after a reboot
--
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 subscribed to
74 matches
Mail list logo
