On Tue, 24 Jan 2017 11:53:55 +0100
Justus Winter wrote:
> Can you please describe in detail what you were doing so that we can
> recreate the problem? You can create a throwaway environment for
> experimentation by setting the environment variable GNUPGHOME to a
> temporary directory, like so (a
On Sat, 21 Jan 2017 11:55:46 +0100
Peter Lebbing wrote:
> You should append a ! to the key ID. This specifies you want this
> specific key and not the keyset to which it belongs.
Thanks for the hint! This did indeed fix my problem.
Regards,
Luis
pgp7ae65VL0gg.pgp
Description: OpenPGP digital
ot;, but it still looks like a bug to me.
Any ideas how this could happen?
Potentially relevant facts:
* The new key's userid collides with that of my old key.
* I'm using the setting "tofu-default-policy unknown".
Regards,
Luis Ressel
__
be used? I've tried
passing in the subkey ID via the '-u'-option, but this didn't work.
I'm using GnuPG 2.1.17.
Regards,
Luis Ressel
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
filesystem entry just reprents the socket that gnupg uses to
communicate with gpg-agent. It's not a file, and no data is stored in
it.
Regards,
Luis Ressel
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
which caused the issue, and 1.7.5 fixes it again.
Thanks for your help, and sorry about the noise!
Regards,
Luis Ressel
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Hello,
since I've upgraded to libgcrypt 1.7.5, gpg emits the warning 'Warning:
using insecure memory!' (and hence refuses to run, since my config file
includes 'require-secmem').
Any hints for debugging this issue would the greatly appreciat
r
the keyservers to deny such requests?)
dirmngr also seems to have problems with hkps certificate checking for
keyserver addresses with round-robin DNS, but I need to examine this
further before I can provide details.
Regards,
Luis Ressel
--
Luis Ressel
GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5
Huh? It shouldn't be neccessary at all to enter your passphrase for
encryption...
--
Luis Ressel
GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD
signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnup
Adding "IdentitiesOnly no" to the top of your ~/.ssh/config should
help.
Regards,
Luis Ressel
signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
ce which is supposed to be open? That sounds nasty and
basically means there could even be backdoors in the implementation, not
only in the underlying system...
Regards,
Luis Ressel
signature.asc
Description: PGP signature
___
Gnupg-users mailing list
s SHA512 SHA384 SHA256 SHA224
s2k-cipher-algo AES256
s2k-digest-algo SHA512
(I added Camellia and CAST5 because 3DES gets forcibly added at the end
and I'd still prefer those two over 3DES...)
Regards,
Luis Ressel
--
Luis Ressel
GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029
error seems to be
"ccid-driver: invalid response for S-block (Change-IFSD)". Does anyone
have an idea about this?
I'll use pcscd if I have to, but I'd rather prefer the internal driver
if it's possible to fix this problem.
Regards,
Luis Ressel
--
Luis Ressel
GPG fpr: F08D 2
error seems to be
"ccid-driver: invalid response for S-block (Change-IFSD)". Does anyone
have an idea about this?
I'll use pcscd if I have to, but I'd rather prefer the internal driver
if it's possible to fix this problem.
Regards,
Luis Ressel
--
Luis Ressel
GPG
14 matches
Mail list logo
