-
Notifications
You must be signed in to change notification settings - Fork 13
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
client: Add a generic Secret type #151
Conversation
2dcc366
to
37e6983
Compare
01e89f6
to
c31e34a
Compare
I guess before we merge this, we should investigate if it is ok to store the content-type as an attribute. If that is the case, we can also make use of that in the portal backend implementation as it would also be relevant for the server side implementation. |
gnome-keyring-daemon never stores or cares about the content-type, on the other hand, kwallet stores it in an attribute https://invent.kde.org/frameworks/kwallet/-/blob/master/src/runtime/kwalletd/kwalletfreedesktopcollection.h#L16 named I guess we should store it as well, maybe named differently with a fallback for Kwallet use case |
c31e34a
to
435115e
Compare
Avoids the duplicated types we have all over the place. - We still don't make use of the content-type when creating or retrieving portal secrets - We still don't make use of content-type when retrieving dbus items But it is an improvement over the current status. Fixes #133
Share the same code as the portal key
Makes uses of the content-type from the DBus API and just hack around for the portal backend until we figure out whether it makes sense to store the content-type as an attribute
435115e
to
3fbbf46
Compare
Merging for now, we can add content-type storage as an attribute later on as it wouldn't conflict with the changes done in this PR. |
See commits.