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
Is your feature request related to a problem? Please describe.
The current size of 2048 for RSA keys is not considered adequate.
Describe the solution you'd like
AFAICT, the change needs to be made here. This might be a quick/easy change, only affecting new key creation and encryption, as long as
it won't break existing encryption functionality
and won't require users to replace their keys.
Anyone who wishes to use the larger key size can then manually remove encryption, replace their key and re-encrypt.
I don't see a way to replace the encryption keys in either the GUI or the scripting/plugin API. This would need to be implemented and documented, including the re-encryption (with the new key) of any encrypted items/tabs.
The text was updated successfully, but these errors were encountered:
akwala
changed the title
Increase PGP encryption key size to 4096 (or at least 3072 which is GPG's default) and replace the keys.
Increase PGP encryption key size to 4096 (or at least 3072 which is GPG's default) ~~and replace the keys~~.
Jul 28, 2023
akwala
changed the title
Increase PGP encryption key size to 4096 (or at least 3072 which is GPG's default) ~~and replace the keys~~.
Increase PGP encryption key size to 4096 (or at least 3072 which is GPG's default).
Jul 28, 2023
Is your feature request related to a problem? Please describe.
The current size of 2048 for RSA keys is not considered adequate.
Describe the solution you'd like
AFAICT, the change needs to be made here. This might be a quick/easy change, only affecting new key creation and encryption, as long as
Anyone who wishes to use the larger key size can then manually remove encryption, replace their key and re-encrypt.
I don't see a way to replace the encryption keys in either the GUI or the scripting/plugin API. This would need to be implemented and documented, including the re-encryption (with the new key) of any encrypted items/tabs.The text was updated successfully, but these errors were encountered: