-
Notifications
You must be signed in to change notification settings - Fork 86
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
kwallet support #66
base: master
Are you sure you want to change the base?
kwallet support #66
Conversation
the kwallet (kde) backend communicates through dbus with the kwalletd. it is modeled after the qtkeychain implementation [1]. like qtkeychain, the keyring backend tries to get the kwallet's 'networkWallet' if this fails the 'secret service' is used as before. kwallet is tried first as the 'secrets service' may exists on systems running kde but it's very unlikely kwallet is running on non kde systems. [1] https://github.com/frankosterfeld/qtkeychain Signed-off-by: Martin Gysel <me@bearsh.org>
Signed-off-by: SoMuchForSubtlety <jakob@ahrer.dev>
Signed-off-by: SoMuchForSubtlety <jakob@ahrer.dev>
Signed-off-by: SoMuchForSubtlety <jakob@ahrer.dev>
afaac55
to
1a56a51
Compare
I see multiple possible issues with this change:
I let @mikkeloscar decide if it's great or not. |
I had to change the signature of Same for the errors, in order to make them accessible in the |
Any progress? @mikkeloscar @SoMuchForSubtlety. Looks like 99designs/keyring supports KWallet. |
Is this still being actively developed? |
I would need feedback from someone from the zalando team to continue. I ended up only using go-keyring for macOS and falling back to 99designs/keyring for everything else. |
Maybe suggest the change for the SecretService.Delete wrapper type? I hope this helps. |
I have lost track of this one, but will have a look tomorrow and give some feedback. Sorry for letting you hanging like this @SoMuchForSubtlety |
I have now had a look and I think it looks quite good. I believe it's ok to break the public interface for the SecretService interface as we only really aim to offer stable support for the public It would be good if you could provide a small guide for the steps needed to migrate in case anyone depends on the Also the PR needs a rebase :) |
Nice! Looking forward to trying this out. |
Any news when this is going to be merged? |
Kwallet recently added support for Secret Service API. |
Looks like this does not work as "plain" Algorithm is not supported. Probably either kwallet should add support for plain, or maybe
edit: fwiw I've created an issue with kwallet to support plain as well: https://invent.kde.org/frameworks/kwallet/-/issues/3 |
FYI kwallet since plasma frameworks 5.97.0 supports the secrets api https://kde.org/announcements/frameworks/5/5.97.0/#:~:text=Introduce%20Secret%20Service%20API |
This PR replaces #52 from @bearsh