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
RainLoop version, browser, OS:
1.11.3, chrome, windows 10 pro Expected behavior and actual behavior:
Sign email with gpg
Attempted signature produces algorithm null error from openpgp
Steps to reproduce the problem:
Import key
Write email
Attempt to sign
Logs or screenshots:
Screenshots to follow. Same exact key works / signs fine from pgp or pgp2 command line and text file. Dsa 4096 key with cs usage on main key and e on subkey.
The text was updated successfully, but these errors were encountered:
ok, strange, and maybe you can help educate me. so as i stated, the same key worked fine signing wise from the gpg or gpg2 cli. so i went ahead and instead tried importing an older backup of the same key i had on disk into rainloop and now it works fine. i removed said key from my localhost's gpg keyring and re-imported the older backup via gpg cli and it seems as it did before. so I'm confused. why did it work this time?
i had also tried exporting the prior key from my keyring, removed it from the keyring, and re-imported it. the same ascii armored text as i tried in rainloop. and it worked in gpg cli but not rainloop.
RainLoop version, browser, OS:
1.11.3, chrome, windows 10 pro
Expected behavior and actual behavior:
Sign email with gpg
Attempted signature produces algorithm null error from openpgp
Steps to reproduce the problem:
Import key
Write email
Attempt to sign
Logs or screenshots:
Screenshots to follow. Same exact key works / signs fine from pgp or pgp2 command line and text file. Dsa 4096 key with cs usage on main key and e on subkey.
The text was updated successfully, but these errors were encountered: