dolphin_oracle wrote: ↑Thu Dec 28, 2023 4:11 pm
its
supposed to ask for the keyring login if autologin is enabled. I can't say what hilariousness the rpi folks have done to chromium that might change expected behavior, and I'm not particularly worried about it.
my system asks everytime if I'm using autologin.
If always only autologin was enabled, PAM would not have created a login-keyring.
PAM can only unlock at login the "Login"-keyring. A new "Login" keyring will be created the first time with a password-login, e.g after logout/login.
In case if no login-keyring exists, the user would have been asked to enter password twice in order to create another, new, normal "Password"-keyring, to get the secrets stored.
You find in seahorse chrome Master-passwords stored within the deafauls Password-keyring.
Next time you login with password, it would offer you enable to unlock the normal Password-keyring at login.
Technically gnome-keying will save/store the protecting password of the Default/Password-keying
into the new Login-Keyring, and PAM will unlock the Login-keyring and gnome-keyring-daemon will provide the secretes stored in the additional normal Password-Keyring.
I'm nor clear, why without having a Login-keyring (due to autologin)
a normal Password-keying would have been unlocked.
But the way I check those is by using seahorse.
