Re: [gentoo-user] GPG problem

[w...@op.pl]

Dnia 2022-07-10, o godz. 10:08:31
the...@sys-concept.com napisał(a):


> Did you make/or have a backup of your .gpg directory?
> 
> Run:  gpg --list-secret-keys --with-keygrip
> Does it show Keygrip =

No, I don't have the copy (my mistake!). It shows correct keygrip,
which (obviously) doesn't exist as a *.key file in my private keys.

-- 
xWK


pgpthKyxVuyH_.pgp
Description: Podpis cyfrowy OpenPGP

Re: [gentoo-user] GPG problem

[thelma]

On 7/10/22 02:56, w...@op.pl wrote:

Hello!
Some time ago I have made a backup of my secret key and all the
subkeys, and then deleted by-hand the master secret key by

rm ~/.gnupg/private-keys-v1.d/[keygrip].key

The subkeys were moved to a yubikey. Everything was great. Now I wanted
to import my master key for a moment... and here we have a problem.
Right now what happens, after running

gpg --import secret_key.asc

is:

1) gpg complains:

gpg: key D444252908A80B6D: "sxrmn" not changed
gpg: key D444252908A80B6D/D444252908A80B6D: error sending to
agent: Invalid argument
gpg: key D444252908A80B6D: secret key imported
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: secret keys read: 1
gpg: secret keys unchanged: 1

2) gpg -K is aware of the master secret key, though it says it's not
there:

sec#  ed25519 2022-07-06 [SC]
902404424B39514B6126A2F2D444252908A80B6D
uid[   absolutne   ] sxrmn
ssb>  cv25519 2022-07-06 [E]
ssb>  ed25519 2022-07-06 [S]

3) seret subkeys get imported (now they are back on yubikey, but they
got imported OK)

For reference, the exactly same file on FreeBSD gets imported with no
errors at all. "diff" tells, that key exported from FreeBSD is no
different from the one I try to import to Gentoo. Therefore I guess
it's more a local GPG version problem than problem with the key.
Strangely though I am trying to import the key generated on Gentoo, so
it seems GPG can't import it's own child.

There are however some version differences between FreeBSD and Gentoo.

FreeBSD:
$ gpg --version
gpg (gnuPG) 2.3.3
libgcrypt 1.9.4
Copyright (c) 2021 Free Software Foundation, Inc.


Gentoo:
$ gpg --version
gpg (GnuPG) 2.2.35
libgcrypt 1.9.4-unknown
Copyright (C) 2022 g10 Code GmbH
...

So... any ideas why this happens and what can I do about it?



Did you make/or have a backup of your .gpg directory?

Run:  gpg --list-secret-keys --with-keygrip
Does it show Keygrip =

Re: [gentoo-user] GPG problem

[Dr Rainer Woitok]

xWK,

On Sunday, 2022-07-10 10:56:18 +0200, you wrote:

> ...
> There are however some version differences between FreeBSD and Gentoo.
> 
> FreeBSD:
> $ gpg --version
> gpg (gnuPG) 2.3.3
> libgcrypt 1.9.4
> Copyright (c) 2021 Free Software Foundation, Inc.
> 
> 
> Gentoo:
> $ gpg --version
> gpg (GnuPG) 2.2.35
> libgcrypt 1.9.4-unknown
> Copyright (C) 2022 g10 Code GmbH

Gentoo provides non-stable version 2.3.6-r1.  Maybe this could help?

Sincerely,
  Rainer

[gentoo-user] GPG problem

[w...@op.pl]

Hello!
Some time ago I have made a backup of my secret key and all the
subkeys, and then deleted by-hand the master secret key by

rm ~/.gnupg/private-keys-v1.d/[keygrip].key

The subkeys were moved to a yubikey. Everything was great. Now I wanted
to import my master key for a moment... and here we have a problem.
Right now what happens, after running

gpg --import secret_key.asc

is:

1) gpg complains:

gpg: key D444252908A80B6D: "sxrmn" not changed
gpg: key D444252908A80B6D/D444252908A80B6D: error sending to
agent: Invalid argument
gpg: key D444252908A80B6D: secret key imported
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: secret keys read: 1
gpg: secret keys unchanged: 1

2) gpg -K is aware of the master secret key, though it says it's not
there:

sec#  ed25519 2022-07-06 [SC]
902404424B39514B6126A2F2D444252908A80B6D
uid[   absolutne   ] sxrmn
ssb>  cv25519 2022-07-06 [E]
ssb>  ed25519 2022-07-06 [S]

3) seret subkeys get imported (now they are back on yubikey, but they
got imported OK)

For reference, the exactly same file on FreeBSD gets imported with no
errors at all. "diff" tells, that key exported from FreeBSD is no
different from the one I try to import to Gentoo. Therefore I guess
it's more a local GPG version problem than problem with the key.
Strangely though I am trying to import the key generated on Gentoo, so
it seems GPG can't import it's own child.

There are however some version differences between FreeBSD and Gentoo.

FreeBSD:
$ gpg --version
gpg (gnuPG) 2.3.3
libgcrypt 1.9.4
Copyright (c) 2021 Free Software Foundation, Inc.


Gentoo:
$ gpg --version
gpg (GnuPG) 2.2.35
libgcrypt 1.9.4-unknown
Copyright (C) 2022 g10 Code GmbH
...

So... any ideas why this happens and what can I do about it?

-- 
xWK


pgpGlL1s06rag.pgp
Description: Podpis cyfrowy OpenPGP

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Miroslav Rovis]

On 170406-18:29+0200, Miroslav Rovis wrote:
> On 170406-16:43+0100, Mick wrote:
> > On Thursday 06 Apr 2017 11:10:56 Fernando Rodriguez wrote:
> > > On 04/05/2017 10:22 PM, Miroslav Rovis wrote:
...
> > If the error is "missing key" have you used 'gpg -K ' to see if the 
> > key is in your keyring and also if it is trusted/revoked/expired?  
> > -- 
> > Regards,
> > Mick
> 
> What I would do if I were in your place, Fernando, I would make certain
> the GnuPG install is fine, by starting from scratch, even making a new
> key. And if that worked fine, it could be the old keys of yours.
> 
> (BTW, I do use ecryption sometimes and signing very much, but I'm not an
> expert. ;-) E.g., I've never used debugging yet.)
> 
> -- 

How could I have forgotten. Try the above, and if the issue persists,
ask here:

http://lists.gnupg.org/mailman/listinfo/gnupg-users

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Miroslav Rovis]

On 170406-16:43+0100, Mick wrote:
> On Thursday 06 Apr 2017 11:10:56 Fernando Rodriguez wrote:
> > On 04/05/2017 10:22 PM, Miroslav Rovis wrote:
> > > On 170405-18:01-0400, Fernando Rodriguez wrote:
> > >> Hello,
> > >> 
> > >> After a recent update I'm getting this error whenever I try to encrypt
> > >> 
> > >> or decrypt using gnupg. Here's error:
> > >>> gpg: selftest for CTR failed - see syslog for details
> > >>> gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
> > >>> Aborted
> > >> 
> > >> And the syslog:
> > >>> gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext
> > >>> mismatch)
> > >> 
> > >> It started after a recent update that included gnupg and libgcrypt. The
> > >> versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After
> > >> the update 1.7.6 and 2.1.18 respectively. I tried downgrading both
> > >> packages but it didn't help.
> > >> 
> > >> I tried to delete the whole ~/.gnupg directory and re-import the keys
> > >> but it fails with the same error.
> > >> 
> > >> I have another keyring on the same machine that I use with the --homedir
> > >> option and I have not problems with it.
> > >> 
> > >> When I try to generate a new key I get the following error:
> > >>> Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
> > >>> We need to generate a lot of random bytes. It is a good idea to perform
> > >>> some other action (type on the keyboard, move the mouse, utilize the
> > >>> disks) during the prime generation; this gives the random number
> > >>> generator a better chance to gain enough entropy.
> > >>> gpg: agent_genkey failed: Missing key
> > >>> Key generation failed: Missing key
> > >> 
> > >> Any ideas?
> > > 
> > > I tried some decryption. No issues here:
> > > 
> > > $ gpg --version
> > > gpg (GnuPG) 2.1.20
> > > libgcrypt 1.7.6
> > > Copyright (C) 2017 Free Software Foundation, Inc.
> > > License GPLv3+: GNU GPL version 3 or later
> > >  This is free software: you are free
> > > to change and redistribute it. There is NO WARRANTY, to the extent
> > > permitted by law.
> > > 
> > > Home: /home/miro/.gnupg
> > > Supported algorithms:
> > > Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
> > > Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
> > > 
> > > CAMELLIA128, CAMELLIA192, CAMELLIA256
> > > 
> > > Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
> > > Compression: Uncompressed, ZIP, ZLIB, BZIP2
> > > $
> > > 
> > > It could be something else, or your Gnupg installation is somehow
> > > broken...
> > 
> > I took the entire .gnupg from the same machine I exported the key from
> > and copied it over to this machine. Now I can at least sign messages but
> > encryption/decryption still fails with the same error.
> 
> If the error is "missing key" have you used 'gpg -K ' to see if the 
> key is in your keyring and also if it is trusted/revoked/expired?  
> -- 
> Regards,
> Mick

What I would do if I were in your place, Fernando, I would make certain
the GnuPG install is fine, by starting from scratch, even making a new
key. And if that worked fine, it could be the old keys of yours.

(BTW, I do use ecryption sometimes and signing very much, but I'm not an
expert. ;-) E.g., I've never used debugging yet.)

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Mick]

On Thursday 06 Apr 2017 11:10:56 Fernando Rodriguez wrote:
> On 04/05/2017 10:22 PM, Miroslav Rovis wrote:
> > On 170405-18:01-0400, Fernando Rodriguez wrote:
> >> Hello,
> >> 
> >> After a recent update I'm getting this error whenever I try to encrypt
> >> 
> >> or decrypt using gnupg. Here's error:
> >>> gpg: selftest for CTR failed - see syslog for details
> >>> gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
> >>> Aborted
> >> 
> >> And the syslog:
> >>> gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext
> >>> mismatch)
> >> 
> >> It started after a recent update that included gnupg and libgcrypt. The
> >> versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After
> >> the update 1.7.6 and 2.1.18 respectively. I tried downgrading both
> >> packages but it didn't help.
> >> 
> >> I tried to delete the whole ~/.gnupg directory and re-import the keys
> >> but it fails with the same error.
> >> 
> >> I have another keyring on the same machine that I use with the --homedir
> >> option and I have not problems with it.
> >> 
> >> When I try to generate a new key I get the following error:
> >>> Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
> >>> We need to generate a lot of random bytes. It is a good idea to perform
> >>> some other action (type on the keyboard, move the mouse, utilize the
> >>> disks) during the prime generation; this gives the random number
> >>> generator a better chance to gain enough entropy.
> >>> gpg: agent_genkey failed: Missing key
> >>> Key generation failed: Missing key
> >> 
> >> Any ideas?
> > 
> > I tried some decryption. No issues here:
> > 
> > $ gpg --version
> > gpg (GnuPG) 2.1.20
> > libgcrypt 1.7.6
> > Copyright (C) 2017 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> >  This is free software: you are free
> > to change and redistribute it. There is NO WARRANTY, to the extent
> > permitted by law.
> > 
> > Home: /home/miro/.gnupg
> > Supported algorithms:
> > Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
> > Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
> > 
> > CAMELLIA128, CAMELLIA192, CAMELLIA256
> > 
> > Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
> > Compression: Uncompressed, ZIP, ZLIB, BZIP2
> > $
> > 
> > It could be something else, or your Gnupg installation is somehow
> > broken...
> 
> I took the entire .gnupg from the same machine I exported the key from
> and copied it over to this machine. Now I can at least sign messages but
> encryption/decryption still fails with the same error.

If the error is "missing key" have you used 'gpg -K ' to see if the 
key is in your keyring and also if it is trusted/revoked/expired?  
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Fernando Rodriguez]

On 04/06/2017 11:10 AM, Fernando Rodriguez wrote:

On 04/05/2017 10:22 PM, Miroslav Rovis wrote:

On 170405-18:01-0400, Fernando Rodriguez wrote:

Hello,

After a recent update I'm getting this error whenever I try to encrypt
or decrypt using gnupg. Here's error:


gpg: selftest for CTR failed - see syslog for details
gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
Aborted


And the syslog:


gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext
mismatch)




It started after a recent update that included gnupg and libgcrypt. The
versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After
the update 1.7.6 and 2.1.18 respectively. I tried downgrading both
packages but it didn't help.

I tried to delete the whole ~/.gnupg directory and re-import the keys
but it fails with the same error.

I have another keyring on the same machine that I use with the --homedir
option and I have not problems with it.

When I try to generate a new key I get the following error:


Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Missing key
Key generation failed: Missing key




Any ideas?


I tried some decryption. No issues here:

$ gpg --version
gpg (GnuPG) 2.1.20
libgcrypt 1.7.6
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/miro/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
$

It could be something else, or your Gnupg installation is somehow
broken...


I took the entire .gnupg from the same machine I exported the key from
and copied it over to this machine. Now I can at least sign messages but
encryption/decryption still fails with the same error.


And that could mean that it's been broken for a while because I rarely 
use this key for encrypting/decrypting. I use it for signing and 
verifying signatures mostly. Just before I deleted the old keyring I was 
getting an error when signing a commit. So perhaps the problem existed 
before the update and just surfaced when I deleted the old keyring.



--

Fernando Rodriguez

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Fernando Rodriguez]

On 04/05/2017 10:22 PM, Miroslav Rovis wrote:

On 170405-18:01-0400, Fernando Rodriguez wrote:

Hello,

After a recent update I'm getting this error whenever I try to encrypt
or decrypt using gnupg. Here's error:


gpg: selftest for CTR failed - see syslog for details
gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
Aborted


And the syslog:


gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext mismatch)




It started after a recent update that included gnupg and libgcrypt. The
versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After
the update 1.7.6 and 2.1.18 respectively. I tried downgrading both
packages but it didn't help.

I tried to delete the whole ~/.gnupg directory and re-import the keys
but it fails with the same error.

I have another keyring on the same machine that I use with the --homedir
option and I have not problems with it.

When I try to generate a new key I get the following error:


Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Missing key
Key generation failed: Missing key




Any ideas?


I tried some decryption. No issues here:

$ gpg --version
gpg (GnuPG) 2.1.20
libgcrypt 1.7.6
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/miro/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
$

It could be something else, or your Gnupg installation is somehow
broken...


I took the entire .gnupg from the same machine I exported the key from 
and copied it over to this machine. Now I can at least sign messages but 
encryption/decryption still fails with the same error.



--

Fernando Rodriguez

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Fernando Rodriguez]

On 04/05/2017 10:22 PM, Miroslav Rovis wrote:

On 170405-18:01-0400, Fernando Rodriguez wrote:

Hello,

After a recent update I'm getting this error whenever I try to encrypt
or decrypt using gnupg. Here's error:


gpg: selftest for CTR failed - see syslog for details
gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
Aborted


And the syslog:


gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext mismatch)




It started after a recent update that included gnupg and libgcrypt. The
versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After
the update 1.7.6 and 2.1.18 respectively. I tried downgrading both
packages but it didn't help.

I tried to delete the whole ~/.gnupg directory and re-import the keys
but it fails with the same error.

I have another keyring on the same machine that I use with the --homedir
option and I have not problems with it.

When I try to generate a new key I get the following error:


Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Missing key
Key generation failed: Missing key




Any ideas?


I tried some decryption. No issues here:

$ gpg --version
gpg (GnuPG) 2.1.20
libgcrypt 1.7.6
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/miro/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
$

It could be something else, or your Gnupg installation is somehow
broken...



Thanks. Here's the output of gpg --gen-key --debug-all in case anyone 
else can help.



$ gpg --gen-key --debug-all
gpg: Note: no default option file '/home/fernan/.gnupg/gpg.conf'
gpg (GnuPG) 2.1.15; Copyright (C) 2016 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat 
trust hashing cardio ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: directory '/home/fernan/.gnupg' created
gpg: new configuration file '/home/fernan/.gnupg/dirmngr.conf' created
gpg: new configuration file '/home/fernan/.gnupg/gpg.conf' created
gpg: DBG: fd_cache_invalidate (/home/fernan/.gnupg/pubring.kbx)
gpg: DBG: iobuf-1.0: open '/home/fernan/.gnupg/pubring.kbx' 
desc=file_filter(fd) fd=3
gpg: DBG: iobuf-1.0: close 'file_filter(fd)'
gpg: DBG: /home/fernan/.gnupg/pubring.kbx: close fd/handle 3
gpg: DBG: fd_cache_close (/home/fernan/.gnupg/pubring.kbx) new slot created
gpg: DBG: iobuf-*.*: ioctl '/home/fernan/.gnupg/pubring.kbx' invalidate
gpg: DBG: fd_cache_invalidate (/home/fernan/.gnupg/pubring.kbx)
gpg: DBG: did (/home/fernan/.gnupg/pubring.kbx)
gpg: keybox '/home/fernan/.gnupg/pubring.kbx' created
Note: Use "gpg2 --full-gen-key" for a full featured key generation dialog.

GnuPG needs to construct a user ID to identify your key.

Real name: fsadfas
Email address: f...@fdsa.com
You selected this USER-ID:
"fsadfas "

Change (N)ame, (E)mail, or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: DBG: chan_4 <- OK Pleased to meet you, process 18814
gpg: DBG: connection to agent established
gpg: DBG: chan_4 -> RESET
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION ttyname=/dev/pts/2
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION ttytype=xterm
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION display=:0
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION xauthority=/tmp/xauth-1000-_0
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION 
putenv=DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-2FF2vYbCnV,guid=883de1ea15755281b1dbb77b58e64397
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION lc-ctype=en_US.utf8
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION lc-messages=en_US.utf8
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> GETINFO version
gpg: DBG: chan_4 <- D 2.1.15
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION allow-pinentry-notify
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> AGENT_ID
gpg: DBG: chan_4 <- ERR 67109139 Unknown IPC command 
gpg: DBG: chan_4 -> RESET
gpg: D

Re: [gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Miroslav Rovis]

On 170405-18:01-0400, Fernando Rodriguez wrote:
> Hello,
> 
> After a recent update I'm getting this error whenever I try to encrypt 
> or decrypt using gnupg. Here's error:
> 
> > gpg: selftest for CTR failed - see syslog for details
> > gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
> > Aborted
> 
> And the syslog:
> 
> > gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext mismatch)
> 
> 
> 
> It started after a recent update that included gnupg and libgcrypt. The 
> versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After 
> the update 1.7.6 and 2.1.18 respectively. I tried downgrading both 
> packages but it didn't help.
> 
> I tried to delete the whole ~/.gnupg directory and re-import the keys 
> but it fails with the same error.
> 
> I have another keyring on the same machine that I use with the --homedir 
> option and I have not problems with it.
> 
> When I try to generate a new key I get the following error:
> 
> > Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
> > We need to generate a lot of random bytes. It is a good idea to perform
> > some other action (type on the keyboard, move the mouse, utilize the
> > disks) during the prime generation; this gives the random number
> > generator a better chance to gain enough entropy.
> > gpg: agent_genkey failed: Missing key
> > Key generation failed: Missing key
> >
> >
> 
> Any ideas?

I tried some decryption. No issues here:

$ gpg --version
gpg (GnuPG) 2.1.20
libgcrypt 1.7.6
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/miro/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
$

It could be something else, or your Gnupg installation is somehow
broken... 

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

[gentoo-user] gpg: selftest for CTR failed - see syslog for details

[Fernando Rodriguez]

Hello,

After a recent update I'm getting this error whenever I try to encrypt 
or decrypt using gnupg. Here's error:



gpg: selftest for CTR failed - see syslog for details
gpg: O j: ... this is a bug (seskey.c:61:make_session_key)
Aborted


And the syslog:


gpg[8945]: Libgcrypt warning: AES-CTR-128 test failed (plaintext mismatch)




It started after a recent update that included gnupg and libgcrypt. The 
versions before the update where libgcrypt-1.7.3 and gnupg-2.1.15. After 
the update 1.7.6 and 2.1.18 respectively. I tried downgrading both 
packages but it didn't help.


I tried to delete the whole ~/.gnupg directory and re-import the keys 
but it fails with the same error.


I have another keyring on the same machine that I use with the --homedir 
option and I have not problems with it.


When I try to generate a new key I get the following error:


Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Missing key
Key generation failed: Missing key




Any ideas?


--

Fernando Rodriguez

[gentoo-user] gpg-agent crach on arm

[Maxime Brachet]

Hi,

I installed gnupg 2.0.16-r2 (and r1 previously) on the AC100 which is
arm based.
When I start gpg-agent i got this error :  

$ gpg-agent 
*** longjmp causes uninitialized stack frame ***: gpg-agent terminated
Aborted

there is a bugfix in ubuntu :
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/599862

I haven't find any references for gentoo.

If anyone has an idea.

Thanks,

Maxime.

[gentoo-user] gpg-agent - connection to .gnupg/log-socket refused

[Mick]

This is what I get when I try to launch the gpg-agent from a terminal:
==
$ eval "$(gpg-agent --daemon)"
can't connect to `/home/michael/.gnupg/log-socket': Connection refused
==

No idea why.  Can I fix it?

This is what the permissions look like:
==
$ ls -la /home/michael/.gnupg/log-socket
srwxr-xr-x 1 michael users 0 Jun 10 22:07 /home/michael/.gnupg/log-socket
==
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list

[gentoo-user] gpg-agent not setting environment correctly.

[abhay]

Hello,

I am trying to setup KMail to use GnuPG. I have emerged unstable gnupg 
(1.9.19), gpg-agent (1.9.19) and pinentry (0.7.2-r1). I am now trying to 
setup gpg-agent and have followed documentation on gentoo site but the 
problem is that even after setting the agent-startup.sh the way it explains, 
the environment is not getting updated. I get the following results when 
trying to know about gpg agent's env

$ $GPG_AGENT_INFO
bash: /tmp/gpg-roleYu/S.gpg-agent:8297:1: No such file or directory

Now, even though gpg-agent is working as daemon, KMail asks for password 
everytime I try to send a signed mail and complains that gpg-agent is not 
running. I have googled but can not find a solution so if someone who is 
running KMail and gpg-agent could give some insights then I will be highly 
thankful.

Abhay
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] gpg

[John Dangler]

Ok. I found out that I have gpg setup right.  I also know that if I enable
passphrases for sending mail, and don't use the gpg agent in enigmail, mail
works great!

However, the docs for enigmail also say that you can set "no passphrase for
this user" and set "use gpg agent for passphrase management", but that
borks.

Anyone tried this successfully?

As an OT question, I saw where you can upload your keys to a keyserver.  Is
that the preferred method of validating/trusting others ?

John D


-Original Message-
From: John Dangler [mailto:[EMAIL PROTECTED] 
Sent: Saturday, August 27, 2005 8:43 PM
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] gpg

I setup gpg and also set up enigmail to use my key and signature.
when I send an email message I get the following:
Error - bad passphrase
/usr/bin/gpg -charset utf8 -batch -no-tty -status-fd 2 -clearsign
-digest-algo sha1 -u [EMAIL PROTECTED] -passphrase-fd 0 -no-use-agent

gpg: skipped "<[EMAIL PROTECTED]>": bad passphrase

gpg: [stdin]: clearsign failed: bad passphrase

any input, as always, is greatly appreciated.

John D



-- 
gentoo-user@gentoo.org mailing list




-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] gpg

[John Dangler]

I setup gpg and also set up enigmail to use my key and signature.
when I send an email message I get the following:
Error - bad passphrase
/usr/bin/gpg -charset utf8 -batch -no-tty -status-fd 2 -clearsign
-digest-algo sha1 -u [EMAIL PROTECTED] -passphrase-fd 0 -no-use-agent

gpg: skipped "<[EMAIL PROTECTED]>": bad passphrase

gpg: [stdin]: clearsign failed: bad passphrase

any input, as always, is greatly appreciated.

John D



-- 
gentoo-user@gentoo.org mailing list