Open hualet opened 2 months ago
The project is aiming to replace gnome-keyring, and ultimately kwallet as well.
Will this project consider integrating modern biometric authentication methods?
I don't understand what kind of integration you mean? To unlock the keyring you mean?
The project is aiming to replace gnome-keyring, and ultimately kwallet as well.
Will this project consider integrating modern biometric authentication methods?
I don't understand what kind of integration you mean? To unlock the keyring you mean?
oh, sorry. I mean gnome-keyring needs user's password to unlock the keyring during user login, but we have fingerprint, face recogonition etc. to login nowadays, then the keyring will stay locked and popup a input dialog for keyring password, which is very disturbing, will this project try to solve this problem?
Yes sure, but that is usually handled by a pam module. The gnome keyring daemon should auto unlock at login.
Whether we should/could support other login mechanisms for unlocking the keyring is a future question that can be handled separately once we have the basics working properly.
I will keep this issue open but would you mind updating the issue title/description to explain what you meant exactly? Thank you
I think things like passkeys or the webauthn standard in general would also be handled by pam modules and oo7 would store the keys encrypted? And will oo7 handle integration with tpm and security keys in this aspect or would that be integrated directly as pam modules?
The project is aiming to replace gnome-keyring, and ultimately kwallet as well.
Oh, so is the goal to streamline the passwords, certificates, passkeys, and overall sensitive data stack on Linux? Like Apple's Keychain?
I think things like passkeys or the webauthn standard in general would also be handled by pam modules and oo7 would store the keys encrypted? And will oo7 handle integration with tpm and security keys in this aspect or would that be integrated directly as pam modules?
I am not involved in those efforts, so I can't answer something I know nothing about.
Oh, so is the goal to streamline the passwords, certificates, passkeys, and overall sensitive data stack on Linux? Like Apple's Keychain?
No, it started as just replacing libsecret, which requires implementing the file backend used by gnome-keyring for the sandboxed use case -> why not implement also the server side implementation of the Secrets dbus interface.
Whether the scope will grow with time, I don't know. It depends on individual contributions & the community at large I guess.
original issue:
updating title/desc for better understanding:
gnome-keyring needs user's password to unlock the keyring during user login, but when new mechanims (like fingerprint, face recogonition etc.) are used, the keyring will stay locked and popup a input dialog for keyring password, that is very disturbing.