You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, jrnl uses keyring to save passwords on the keyring backend supported by the operating system (e.g. Keychain on macOS or Windows Credential Locker on Windows). However, keyring has support for some third-party backends, including the popular password manager 1password through the onepassword-keyring project. It would be nice to implement this in jrnl.
Example Usage
I'm not sure how best to configure this. Maybe we add a new keyring field in the config file.
Otherwise, it shouldn't act too differently than how Keychain works with jrnl on MacOS: it would prompt the user to unlock the vault with a password, then the vault would return the specific jrnl password to jrnl.
Other Information
No response
The text was updated successfully, but these errors were encountered:
Use Case/Motivation
Currently, jrnl uses keyring to save passwords on the keyring backend supported by the operating system (e.g. Keychain on macOS or Windows Credential Locker on Windows). However, keyring has support for some third-party backends, including the popular password manager 1password through the onepassword-keyring project. It would be nice to implement this in jrnl.
Example Usage
I'm not sure how best to configure this. Maybe we add a new keyring field in the config file.
Otherwise, it shouldn't act too differently than how Keychain works with jrnl on MacOS: it would prompt the user to unlock the vault with a password, then the vault would return the specific jrnl password to jrnl.
Other Information
No response
The text was updated successfully, but these errors were encountered: