-
Notifications
You must be signed in to change notification settings - Fork 12
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
portal: Add rekeying support for oo7::portal::Keyring #77
Conversation
8e667bd
to
34a5448
Compare
34a5448
to
6edb24e
Compare
6edb24e
to
11256aa
Compare
11256aa
to
d718983
Compare
d718983
to
aff0315
Compare
aff0315
to
1c66645
Compare
1c66645
to
d6b39a7
Compare
Since this also changes the |
964002c
to
04e1afe
Compare
04e1afe
to
c8ea581
Compare
c8ea581
to
3a960ee
Compare
e8f8bb5
to
dc77973
Compare
dc77973
to
ae5bcc0
Compare
ae5bcc0
to
e8ede38
Compare
e8ede38
to
60c83bb
Compare
60c83bb
to
dcf63b7
Compare
dcf63b7
to
665d73e
Compare
Although it is not necessary to update the `salt` value before a password/secret change through `oo7::portal::Keyring.change_secret()`. It would be a good practice to do so. Also, updates the `Keyring.modified_time` in `change_secret()` See: #77 (comment) Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
This change adds `change_secret()` to `oo7::portal::Keyring` API. `change_secret()` change/update the secret associated with a keyring. Note: we need this change for the sever side implementation. Fixes: #47 Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
Although it is not necessary to update the `salt` value before a password/secret change through `oo7::portal::Keyring.change_secret()`. It would be a good practice to do so. Also, updates/resets the remaining Keyring content. `modified_time` field is not update here. Cleaned up a few whitespaces. See: #77 (comment) Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
77185a0
to
96d8f92
Compare
Although it is not necessary to update the `salt` value before a password/secret change through `oo7::portal::Keyring.change_secret()`. It would be a good practice to do so. Also, updates/resets the remaining Keyring content. `modified_time` field is not update here. Cleaned up a few whitespaces. See: #77 (comment) Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
96d8f92
to
5e0fea3
Compare
Although it is not necessary to update the `salt` value before a password/secret change through `oo7::portal::Keyring.change_secret()`. It would be a good practice to do so. Also, updates/resets the remaining Keyring content. `modified_time` field is not update here. See: #77 (comment) Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
5e0fea3
to
4a97e2f
Compare
Also added a comment to indicate setting the new key Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
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.
Looks good to me, but would appreciate a review / an ack from @ueno
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.
LGTM, thanks for all the work here!
Although it is not necessary to update the `salt` value before a password/secret change through `oo7::portal::Keyring.change_secret()`. It would be a good practice to do so. Also, updates/resets the remaining Keyring content. `modified_time` field is not update here. See: #77 (comment) Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
Although it is not necessary to update the `salt` value before a password/secret change through `oo7::portal::Keyring.change_secret()`. It would be a good practice to do so. Also, updates/resets the remaining Keyring content. `modified_time` field is not update here. See: #77 (comment) Signed-off-by: Dhanuka Warusadura <dhanuka@gnome.org>
This change adds
change_secret()
tooo7::portal::Keyring
API.change_secret()
change/update the secret associated with a keyring.Note: we need this change for the sever side implementation.
Fixes: #47