fz0x1/jrnl
1
0
Fork 0
mirror of https://github.com/jrnl-org/jrnl.git synced 2025-07-05 07:56:14 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #2 from samuelgregorovic/develop

Browse source 
fix docs conflict
This commit is contained in:
samuelgregorovic 2021-07-17 22:56:29 +02:00 • committed by GitHub
commit 686c256bd5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 115 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/privacy-and-security.md
View file

@ -86,6 +86,18 @@ you have a journal, where that journal file is, and when you last edited it.
With a sufficient power imbalance, someone may be able to force you to unencrypt
it through non-technical means.
## Saved Passwords
When creating an encrypted journal, you'll be prompted as to whether or not you
want to "store the password in your keychain." This keychain is accessed using
the [Python keyring library](https://pypi.org/project/keyring/), which has different
behavior depending on your operating system.
In Windows, the keychain is the Windows Credential Manager (WCM), which can't be locked
and can be accessed by any other application running under your username. If this is
a concern for you, you may not want to store your password.
## Notice any other risks?
Please let the maintainers know by [filing an issue on GitHub](https://github.com/jrnl-org/jrnl/issues).