oo7-daemon ========== oo7-daemon: the new DBus Secret Service provider, initial test results. pull request: https://github.com/bilelmoussaoui/oo7/pull/73 Executing `oo7-daemon`: ``` cd oo7/server cargo run --release ``` ## Test results: - ### `secret-tool`: Initial objects (objectpaths) tree: ``` busctl --user tree org.freedesktop.secrets ```  `oo7-daemon` currently cannot parse existing keyrings in .local/share/keyrings/. Specifically the Login/default keyring. Because, `oo7-daemon` currently doesn't have a Prompt (UI served by the gnome-shell) to retrieve the passwords associated with keyrings. `secret-tool` interacts with the Login keyring. Since `oo7-daemon` cannot load the Login keyring the tests were unsuccessful.  - ### `oo7-cli`: Similar to `secret-tool`, `oo7-cli` also interacts with the Login keyring. But, if there is no Login keyring available, `oo7-cli` will create one for you.   Even though a new keyring (named "Login") is created by `oo7-cli`, creating a new Item (storing a password in the keyring) operation still fails. Note: the keyring just created is unencrypted. Infact currently all the keyrings created based on oo7-daemon as the DBus Secret Service provider will be unencrypted. Because, the oo7-daemon doesn't have a prompt to get a password input. - ### `Seahorse`: Executing Seahorse **without** DBus Secret Service provider:  Executing Seahorse **with** oo7-daemon as the DBus Secret Service provider:  Creating a new keyring with Seahorse:  Now the objects tree:  * Creating a new keyring with Seahorse is possible. And unencrypted keyrings are created. * Newly created keyrings are not shown immediately in Seahorse (the usual behavior). * One needs to close and re-lauch Seahorse to see the newly created keyring.  - Newly created `oo7` keyring is not in the default location.  Storing a password with Seahorse:  - Operation fails and no error messages are visible.