Bug#987298: gdm3: Fails to unlock GNOME keyring when multiple attempts were needed to unlock LUKS

2021-06-06 Thread intrigeri
Hi Simon, Simon McVittie (2021-04-30): > Sorry, I can't work out how to get a system where the bug you reported > would even be relevant. At this stage in the release process I am reluctant > to apply changes that I can't test - please could you describe how I can? Thanks for having considered

Bug#987298: gdm3: Fails to unlock GNOME keyring when multiple attempts were needed to unlock LUKS

2021-04-30 Thread Simon McVittie
Control: tags -1 + moreinfo On Thu, 22 Apr 2021 at 09:37:19 +0100, Simon McVittie wrote: > On Wed, 21 Apr 2021 at 08:33:01 +0200, intrig...@debian.org wrote: > > On LUKS-encrypted systems, by default the GNOME keyring is encrypted > > using the LUKS passphrase typed on boot. pam_gdm unlocks the

Bug#987298: gdm3: Fails to unlock GNOME keyring when multiple attempts were needed to unlock LUKS

2021-04-22 Thread Simon McVittie
On Wed, 21 Apr 2021 at 08:33:01 +0200, intrig...@debian.org wrote: > On LUKS-encrypted systems, by default the GNOME keyring is encrypted > using the LUKS passphrase typed on boot. pam_gdm unlocks the keyring > using that passphrase. So far, so good. Does testing this require any particular

Bug#987298: gdm3: Fails to unlock GNOME keyring when multiple attempts were needed to unlock LUKS

2021-04-21 Thread intrigeri
Package: gdm3 Version: 3.38.2.1-1 Severity: important Hi, On LUKS-encrypted systems, by default the GNOME keyring is encrypted using the LUKS passphrase typed on boot. pam_gdm unlocks the keyring using that passphrase. So far, so good. On current sid, pam_gdm uses the _first_ passphrase that