config: use keyring.get_password() as a workaround for a kwallet bug #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current implementation of the keyring KWallet backend contains a regression: get_credential() returns the password as a string. jaraco/keyring@0b7b41f
MrAnno
force-pushed
the
kwallet-workaround
branch
from
d9014e9
to
c9ca19a
Compare
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation of the keyring KWallet backend contains a regression that breaks the autofill feature of openconnect-sso:
get_credential()returns the password as a string.jaraco/keyring@0b7b41f
(I'm about to report and fix this upstream.)
Using
get_password()is sufficient in my opinion.