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.

Sign up for GitHub

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

Jump to bottom

BUG: gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type #4

Closed
2 tasks
major0 opened this issue Jan 18, 2025 · 0 comments
Closed
2 tasks

BUG: gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type #4

major0 opened this issue Jan 18, 2025 · 0 comments
Labels
bug Something isn't working
Milestone
Full Login

Comments

@major0
Copy link
Owner

major0 commented Jan 18, 2025 •
edited
Loading

When attempting to call Client.GetAddresses() from go-proton-api, we receive the following error:

2025/01/18 07:09:27.772013 WARN RESTY gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type, Attempt 1
2025/01/18 07:09:27.772055 ERROR RESTY gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type
Error: gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type

This is being actively tracked upstream
@major0 major0 added the bug Something isn't working label Jan 18, 2025
@major0 major0 added this to the Full Login milestone Jan 18, 2025
@major0 major0 closed this as completed in 3bd8e6d Jan 18, 2025
major0 added a commit that referenced this issue Jan 18, 2025
@major0
fix: bad key sig types
0dcf963 
Apparently There are special "proton compatible" branches of gopenpgp
and go-crypto, neither of which are used by the go-proton-api, which is
a little ironic since the go-proton-api requires these features only
found in these proton specific branches.

Fixes: #4
major0 added a commit that referenced this issue Jan 18, 2025
@major0
fix: bad key sig types
b4ab5e2 
Apparently There are special "proton compatible" branches of gopenpgp
and go-crypto, neither of which are used by the go-proton-api, which is
a little ironic since the go-proton-api requires these features only
found in these proton specific branches.

Fixes: #4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Full Login
Development

No branches or pull requests
1 participant
@major0