[Bug 1804408] Comment bridged from LTC Bugzilla

2019-03-04 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-05 02:34 EDT--- IBM bugzilla status-> closed, Fix Released with Bionic,Cosmic and Disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1804408] Comment bridged from LTC Bugzilla

2019-02-14 Thread bugproxy
--- Comment From ifran...@de.ibm.com 2019-02-14 10:50 EDT--- I have upgraded from proposed and retested with a LUKS2 volume using secure keys. I can confirm that it still works as intended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1804408] Comment bridged from LTC Bugzilla

2019-02-14 Thread bugproxy
--- Comment From ifran...@de.ibm.com 2019-02-14 02:55 EDT--- I already did test this as a PPA (2.16-5ubuntu0.1) on Ubuntu 18.10, see a few comments above. Do you want me to test it again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1804408] Comment bridged from LTC Bugzilla

2019-02-06 Thread bugproxy
--- Comment From ifran...@de.ibm.com 2019-02-06 06:56 EDT--- Looks good ! I installed the PPA (2.16-5ubuntu0.1) on Ubuntu 18.10 and configured pam_mount for user 'user' with a LUKS2 encrypted disk using secure keys: /etc/security/pam_mount.conf.xml: When I logon the user, it unlocks

[Bug 1804408] Comment bridged from LTC Bugzilla

2019-02-05 Thread bugproxy
--- Comment From ifran...@de.ibm.com 2019-02-05 03:43 EDT--- We have documented the use of pam_mount with LUKS(2) and secure keys and the PAES cipher in the manual "Pervasive Encryption for Data Volumes" in chapter 5, section "Opening and mounting an encrypted volume at user login":