-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Manjaro] Pius errors #131
Comments
Are you using Debian? |
I'm using Manjaro Linux Deepin x64. |
Sounds like Manjaro installed it as a py3 app instead of a py2 app, incorrectly. py3 support is experimental at best. Your best get is just to pull down a git clone of the repo here, and then cd into the directory and do:
And run it directly from the source tree. Feel free to file a bug upstream againt Manjaro to repackage it properly as well. We're working on PIUS 3.0 which will by full (and only) python 3. |
I have download and build it from source.
|
Maybe run |
I have already have a gpg keyring. On |
Ah yeah, it assumes the ring is in pubring, not keybox format. It should be smarter about that. In the meantime, use |
so it I should use |
no, |
;) 👍 |
I'm have my secret key on a yubikey.
|
You're using py3 again, please use py2. |
Well, I'm not.
and
and I still get the error above |
Oh sorry I read the wrong error. Can you run it in debug mode? Do you have an agent running? |
I have my pgp on a yubikey.
Can you give the commands for me to give you the output?
Enviado através do ProtonMail móvel
…-------- Mensagem Original --------
Ligado 20/06/2019, 00:15, Phil Dibowitz escreveu:
Oh sorry I read the wrong error. Can you run it in debug mode? Do you have an agent running?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, [view it on GitHub](#131?email_source=notifications&email_token=ABKT3BGN47XV6EJOB7UW34DP3K4YNA5CNFSM4HYVBMGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDRIRI#issuecomment-503780421), or [mute the thread](https://github.com/notifications/unsubscribe-auth/ABKT3BEAVPR3Z62C2FZCKC3P3K4YNANCNFSM4HYVBMGA).
|
just run it again with I've never tried it with the key on a yubikey, not sure how well it'll work as it expects the agent to be able to load the key. My suspicion is that the agent says something we don't know about yet that is supposed to tell us to tell you to touch your yubikey. Debug output should help. |
you can reproduce the setup with the Debian Subkeys approach: https://wiki.debian.org/Subkeys We're "handling" this case in GNOME Keysign by ignoring it: https://gitlab.gnome.org/GNOME/gnome-keysign/issues/15 |
My yubikey needs a touch for encryption and signing. It did not ask for such touch (running this command). |
Sorry I never responded to this. My guess is we'll have to do some extra work to support interaction-required key-storage. I would have thought that the agent would sorta handle that, but I guess not. That said, with the DDOS's on the keyservers, and the significant disagreement between the gpg client developer and the new DDOS-resistant keyservers that have made using them near-impossible, I stopped using gpg to sign my email, and stopped running KSPs a few years back, and as such, haven't been very focused on PIUS. So changes of me addressing this soon are pretty low. I will, of course, be happy to help others who are interested in working on it, and I will review PRs in a timely fashion. |
When running
pius -s "...." "...."
I get this error:and if I change
/usr/bin/pius
shebang to#!/usr/bin/python2
I get this error:I need this fixed. Thank you
The text was updated successfully, but these errors were encountered: