Open ghost opened 11 years ago
Thanks, I agree. I do not have much time to work on this myself however. If you could find documentation on that format, it would be much appreciated!
Seahorse displays the secret type as "Google Chrome password" and stores attributes like the following:
submit_element: scheme: 0 action_url: username_value: ssl_valid: 0 origin_url: application: chrome-6717484 signon_realm: username_element: blacklisted_by_user: 0 preferred: 1 date_created: password_element: ****
By contrast, seahorse displays our secret as generic "Password or secret" and we store attributes like the following:
passwordField: hostname: formSubmitURL: mozLoginInfoMagic: loginInfoMagicv1 username: usernameField: ****
I would love to see that too. However, Chrome's format a bit far from being future interop standard — for a start, Chrome/-ium requires the application field to name it :).
It would be nice, if mozilla-gnome-keyring will use exact same entry format as Google Chrome. It would allow to share secrets between browsers.