Skip to content
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

Fix KeyRing issues #3869

Merged
merged 2 commits into from
Mar 26, 2022

Conversation

matthiasblaesing
Copy link
Contributor

No description provided.

…cting disable it

The code path in GnomeLibSecretProvider#enabled relies on
RuntimeException to be thrown in case of errors. Before this change
errors from libsecret were written to the messages.log, but still
allowed NetBeans to enable libsecret to be activated as password wallet.

Closes: apache#3579
The application names for the Gnome Keyring and LibSecret integrations
are derived from the name of the application. That name contains the
release version, so the passwords are lost on each update.

Instead of deriving the name from the application name, GnomeKeyring
and LibSecret are brought in line with the existing implementation of
KWallet and mac OS, where the name is hardcoded.

As the names for GnomeKeyring and LibSecret have to be change at least
once more, they are unified to the KWallet name (which might be
accessed by LibSecret)

Closes: apache#3702
@matthiasblaesing
Copy link
Contributor Author

Both fixed issues were verified (one tested by myself, the second by the reporter), unittests are green I did a self-review.

@matthiasblaesing matthiasblaesing merged commit d195a05 into apache:master Mar 26, 2022
@matthiasblaesing matthiasblaesing deleted the keyring_optimization branch March 26, 2022 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant