Hi André,
On 06/04/2019 21:21, André Ockers wrote:
> which would probably be a bad idea, wouldn't it?
Quite! :-)
Your operating system probably still requires GnuPG 1.4, so you can't
remove it. But you can solemnly pledge not to use it... I wouldn't mess
with the "gpg" binary, though. Don't use
Hi Peter and list,
Op 06-04-19 om 21:02 schreef Peter Lebbing:
> The error message is really unclear, but the problem probably is that
> you should have used "gpg2" instead of "gpg", consistently. So just
> leave "gpg" behind and only use "gpg2" ever. Well, until an updated
> Trisquel drops the o
On 06/04/2019 18:50, Jean-David Beyer via Gnupg-users wrote:
> Mine's bigger than yours (older, too):
>
> $ gpg --version
> gpg (GnuPG) 2.0.14
Yeah, and it's probably high time to put gramps out to pasture as
well... ;-) That's a seriously old, unsupported version.
Peter.
--
I use the GNU Priv
On 06/04/2019 20:24, André Ockers wrote:
>>> gpg: secret key "7CD3FBC8F6005ED5" not found: eof
> I'm using (up to date) Trisquel
>
> $ gpg --version
> gpg (GnuPG) 1.4.20
>
> $ gpg2 --version
> gpg (GnuPG) 2.1.11
> libgcrypt 1.6.5
The error message is really unclear, but the problem probably is t
Hi mr. Reichelt and list,
Op 06-04-19 om 18:32 schreef Markus Reichelt:
> * André Ockers wrote:
>
>> Op 06-04-19 om 15:04 schreef Markus Reichelt:
>>> gpg -a --output an...@ockers.eu.asc.revoke --gen-revoke 7CD3FBC8F6005ED5
>> This leads to the following:
>>
>> gpg: secret key "7CD3FBC8F6005ED5
On 4/6/19 12:32 PM, Markus Reichelt wrote:
> i'm using on slackware64-current (if you are using windows, all hands
> are off)
>
> gpg --version
> gpg (GnuPG) 2.2.15
> libgcrypt 1.8.4
Mine's bigger than yours (older, too):
$ gpg --version
gpg (GnuPG) 2.0.14
libgcrypt 1.4.5
Copyright (C) 2009 Free
* André Ockers wrote:
> Op 06-04-19 om 15:04 schreef Markus Reichelt:
> > gpg -a --output an...@ockers.eu.asc.revoke --gen-revoke 7CD3FBC8F6005ED5
>
> This leads to the following:
>
> gpg: secret key "7CD3FBC8F6005ED5" not found: eof
i'm using on slackware64-current (if you are using windows,
Dear mr. Reichelt,
Thank you for your answer.
Op 06-04-19 om 15:04 schreef Markus Reichelt:
> gpg -a --output an...@ockers.eu.asc.revoke --gen-revoke 7CD3FBC8F6005ED5
This leads to the following:
gpg: secret key "7CD3FBC8F6005ED5" not found: eof
Best regards,
André Ockers
signature.asc
De
* André Ockers wrote:
> But when I tried to do the some thing in Bash I ran into the following:
>
> $ gpg -a --output an...@ockers.eu.asc.revoke --gen-revoke an...@ockers.eu
>
> sec 4096R/F5FE3668 2014-07-31 André Ockers
>
> Which is the fingerprint of the old key.
>
> What happened and wha
Dear all,
After I've created a new key and uploaded it to a key server, I ran into
something when generating a revocation certificate.
In Seahorse, I could select the right (new) key and make a revocation
certificate from there.
But when I tried to do the some thing in Bash I ran into the follow
10 matches
Mail list logo
