xi-keyring

commit

6d9bc9fe0a96469ee864c6755c125991a8e73115

parent

b17e0d2b8b006d299e0ac48afb3729abac0bf235

Author

Tobias Bengfort <tobias.bengfort@posteo.de>

Date

2024-05-10 10:15

README: mention namespaces

Diffstat

1 files changed, 1 insertions, 0 deletions

diff --git a/README.md b/README.md

@@ -37,6 +37,7 @@ for nuance here. These are some of the **ideas** I want to experiment with:
   37    37 -   Allow to configure access rules (always allow, always deny, prompt) per application
   38    38 -   Encrypt the meta data
   39    39 -   Keep the keyring locked as much as possible without impacting user comfort too much. For example, don't unlock automatically on login.
   -1    40 -   Use separate namespaces for different applications, so one application can not access the secrets stored by another.
   40    41 
   41    42 **I am not claiming that this is or ever will be more secure than
   42    43 gnome-keyring.** The gnome-keyring developers are much more experienced with