On 2014-05-26 13:27, Dmitriy Matrosov wrote: > On 05/25/2014 11:22 PM, Christian Kastner wrote: >> I'd appreciate it if you >> could check the contents of /proc/keys right after boot. The fourth >> column should list the remaining time until the key expires, or "perm" >> if the expiry has been reset. > > Hi, Christian. > > Here is the result: > > From initramfs just after password had cached: > 1a0f0935 I--Q--- 1 1m 3f010000 0 0 user cryptkey-reiji: 27 > 21d6c5bf I--Q--- 2 perm 1f3f0000 0 65534 keyring _uid.0: 1 > 2849060a I--Q--- 1 perm 1f3f0000 0 65534 keyring _uid_ses.0: 1 > > Before udev started: > 1a0f0935 I--Q--- 1 58s 3f010000 0 0 user cryptkey-reiji: 27 > 21d6c5bf I--Q--- 2 perm 1f3f0000 0 65534 keyring _uid.0: 1 > 2849060a I--Q--- 1 perm 1f3f0000 0 65534 keyring _uid_ses.0: 1 > > After udev started: > 1a0f0935 I--Q--- 1 4h 3f010000 0 0 user cryptkey-reiji: 27 > 21d6c5bf I--Q--- 2 perm 1f3f0000 0 65534 keyring _uid.0: 1 > 2849060a I--Q--- 1 perm 1f3f0000 0 65534 keyring _uid_ses.0: 1
Well, isn't that strange. I was hoping to see something in the order of a few extra seconds or so, but 4 hours is off by a long shot. I really have no idea what could be causing this. I would have suspected a fishy udev rule, but briefly looking at keyutil's reverse dependencies, I can't find a package with such a rule. I will try to investigate more, but ultimately I believe I will re-assign this bug to udev. Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
