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

Gpg key attempted use produces algorithm: null error #1676

Open
fsantiago07044 opened this issue Apr 18, 2018 · 1 comment
Open

Gpg key attempted use produces algorithm: null error #1676

fsantiago07044 opened this issue Apr 18, 2018 · 1 comment

Comments

@fsantiago07044
Copy link

fsantiago07044 commented Apr 18, 2018

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.

@fsantiago07044
Copy link
Author

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.

??? Thanks for any insight you can offer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant