-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
server: Load and dispatch login/default collection/keyring #142
Conversation
Thanks for the prompt review and I'm sorry for the late response from my side :) |
09d26c7
to
7ff8bfe
Compare
0049157
to
ae3d5a6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
almost there
Also you have access to this repo, use a branch in it to make it easier for me to push quick fixes :) |
That generates and returns a random Secret. Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
Yeah, thanks! But I kinda like this way, I'm learning a lot of Rust from you :) |
Looks good, just squash the last 3 server related commits as they are not clean by themselves and there is little benefit in cleaning them up. Maybe re-change the commit message to "server: Create a keyring when dispatching default/login collections" |
Also add the following changes: Add Error. Load a temporary keyring when dispatching the session collection. Add --login command line option. Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
Done. |
thanks |
Load temporary keyring when dispatching the session collection. Since the session collection is never stored to the disk, loading a temporary keyring is enough.
This change loads and dispatches the login/default collection/keyring into the object tree. This change also adds,
--login
command line option to oo7-daemon.-l, --login
option will read a password from stdin, and use it to unlock the login keyring.