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

Use preferred/main keyring from Mailvelope #7157

Closed
Frederick888 opened this issue Jan 9, 2020 · 4 comments
Closed

Use preferred/main keyring from Mailvelope #7157

Frederick888 opened this issue Jan 9, 2020 · 4 comments

Comments

@Frederick888
Copy link

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.

image

@thomascube
Copy link
Member

At the time of writing that code, the Mailvelope API didn't allow access to the main keyring. I'll check if that changed in the meantime...

@Frederick888
Copy link
Author

Frederick888 commented Jan 9, 2020

@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.

@alecpl
Copy link
Member

alecpl commented Sep 30, 2020

The mailvelope_main_keyring option already is implemented. I think this ticket should be now to make it available to the user through Preferences.

@alecpl alecpl added this to the 1.5-beta milestone Sep 30, 2020
@alecpl
Copy link
Member

alecpl commented Oct 3, 2020

Implemented.

@alecpl alecpl closed this as completed Oct 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants