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
Currently Roundcube uses the unique user id as the keyring identifier in Mailvelope integration. However, as I use GnuPG with YubiKey, it's impossible for me to import my private key into the Roundcube keyring and there doesn't seem to be a way of wiring the GnuPG keys into other keyrings in Mailvelope, either.
Is it possible to allow users to select the main/preferred keyrings from Mailvelope? I think it could also be more convenient for users in some cases if they simply want to share the same keys for different users/websites.
The text was updated successfully, but these errors were encountered:
@thomascube Ah yeah, indeed its client API doesn't allow accessing the main and GnuPG keyrings. The identifiers of these 2 keyrings are localhost|#|mailvelope and localhost|#|gnupg respectively however in the client content script, it's explicitly banned providing host as part of the identifier.
It's probably a design for better security but I think there should be a setting available to make them, especially the GnuPG one, accessible to client API consumers. I guess I can file an issue there to see how the Mailvelope developers think.
Currently Roundcube uses the unique user id as the keyring identifier in Mailvelope integration. However, as I use GnuPG with YubiKey, it's impossible for me to import my private key into the Roundcube keyring and there doesn't seem to be a way of wiring the GnuPG keys into other keyrings in Mailvelope, either.
Is it possible to allow users to select the main/preferred keyrings from Mailvelope? I think it could also be more convenient for users in some cases if they simply want to share the same keys for different users/websites.
The text was updated successfully, but these errors were encountered: