You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I analyzed cryptomator/cryptomator#3476 and was wondering why the user has this issue, although Cryptomator worked on my EndevourOS.
The bottom line is, that kwallet offers a secret service interface for some time now. So on a freshly installed KDE without GNOME keyring installed, you have the following D-Bus service available:
That's exactly the one secret-servicechecks for on startup and GNOME keyring is available from then on as a keychain back end.
The user's problem resulted from the combination of configuring GNOME keyring as the password back end in Cryptomator, but not having a default KDE wallet.
Once you have a default KDE wallet (which is created from KDE, when you first try to save a secret or manually created or kdewallet does it for you), you can even use secret-service and kdewallet interchangeably to save passwords to kwallet and read them from there. The following screenshot shows the result when having two vaults:
I did not test every feature, but as far as I can see, this works flawlessly. However, secret-service using kwallet does not trigger kwallet to create a default KDE wallet, in case it does not exist and that leads to many ugly exceptions in Cryptomator.
The text was updated successfully, but these errors were encountered:
I analyzed cryptomator/cryptomator#3476 and was wondering why the user has this issue, although Cryptomator worked on my EndevourOS.
The bottom line is, that
kwallet
offers a secret service interface for some time now. So on a freshly installed KDE withoutGNOME keyring
installed, you have the following D-Bus service available:That's exactly the one
secret-service
checks for on startup and GNOME keyring is available from then on as a keychain back end.The user's problem resulted from the combination of configuring GNOME keyring as the password back end in Cryptomator, but not having a default KDE wallet.
Once you have a default KDE wallet (which is created from KDE, when you first try to save a secret or manually created or
kdewallet
does it for you), you can even usesecret-service
andkdewallet
interchangeably to save passwords tokwallet
and read them from there. The following screenshot shows the result when having two vaults:I did not test every feature, but as far as I can see, this works flawlessly. However,
secret-service
usingkwallet
does not triggerkwallet
to create a default KDE wallet, in case it does not exist and that leads to many ugly exceptions in Cryptomator.The text was updated successfully, but these errors were encountered: