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

Crash with ed25519/gpg 2.0 #50

Open
ankon opened this issue Feb 7, 2017 · 4 comments
Open

Crash with ed25519/gpg 2.0 #50

ankon opened this issue Feb 7, 2017 · 4 comments
Assignees
Labels
bug waitingonsubmitter Waiting on the sbumitter

Comments

@ankon
Copy link

ankon commented Feb 7, 2017

gpg 2.1 introduced support for ed25519. When using pius with gpg 2.0(.30, mac) and trying to sign such keys pius crashes, rather than reporting that it cannot handle this key type.

@jaymzh
Copy link
Owner

jaymzh commented Feb 7, 2017

Can you provide the stacktrace?

@jaymzh jaymzh self-assigned this Mar 19, 2018
@jaymzh jaymzh added waitingonsubmitter Waiting on the sbumitter bug labels Mar 19, 2018
@jaymzh
Copy link
Owner

jaymzh commented Jul 1, 2019

@ankon ?

@ankon
Copy link
Author

ankon commented Jul 2, 2019

I'm sorry, I missed this notification, and I haven't been using pius since then. I guess best to close this, and see whether it pops up again?

Out of interest, what would be the sensible steps to get a stack trace that would be useful for you?

@jaymzh
Copy link
Owner

jaymzh commented Jul 3, 2019

You said it crashed, so whenever a python app crashes it prints a stacktrace, so just doing whatever you did before.

However, running it with debug mode (-d) would be even more useful.

In short, something like:

pius -r <partykeyring> -s <yourkeyid> -d <keyidthatcausesthecrash>

Aught to do it.

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

No branches or pull requests

2 participants