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
Thank you for this library. I just wanted to point out an interesting edge case. We are using a private key which has no passphrase and the only way I could get it to find and use the key was by putting in a dummy passphrase. Without the dummy passphrase I see the log output
org.c02e.jpgpj.Decryptor: not using decryption key sec ed XXXXXXX
Thanks for pointing out this issue! I'm thinking the best way to handle this, since the JPGPJ API already uses an empty string for the passphrase to signal that the private part of the key should be ignored, is to formalize your dummy passphrase technique with a NO_PASSPHRASE constant in the API. That constant would be given in place of the passphrase to signal that the private part of the key should be used, but without a passphrase, like so:
Add Key.NO_PASSPHRASE constant to signal that a key doesn't use a
passphrase (as well as Key/Subkey.noPassphrase property),
and add unit test to validate a passphrase-less key works
for signing and decryption.
I added that constant to the code (plus a setNoPassphrase() helper to the Key and Subkey classes), and then added a No Passphrase section to the Key Rings wiki page to document how to use passphrase-less keys.
Thank you for this library. I just wanted to point out an interesting edge case. We are using a private key which has no passphrase and the only way I could get it to find and use the key was by putting in a dummy passphrase. Without the dummy passphrase I see the log output
org.c02e.jpgpj.Decryptor: not using decryption key sec ed XXXXXXX
after I put in a dummy pass phrase
org.c02e.jpgpj.Decryptor:using decryption key sec+ed XXXXXXX
The text was updated successfully, but these errors were encountered: