Configuring dirmngr

I'm having trouble configuring dirmngr to use a default keyserver. The current configuration file at .gnupg/dirmngr.conf contains this single line: keyserver hkp://pgp.mit.edu However trying to use --recv-keys always fails: $ gpg --recv-keys 0x194b631ab2da2888 gpg: no valid OpenPGP

Re: E-mail with deniable authentication

Good point. Note: You forgot to reply to list. On 02/09/17 22:11, Lachlan Gunn wrote: > Le 2017-09-03 à 11:48, Mario Castelán Castro a écrit : >> I am well aware of that. Although deniable encryption is not a panacea >> it is an improvement. It gives less power to the correspondent to blackmail.

Re: Documentation of trust model

On 05/09/17 00:58, Mario Castelán Castro wrote: > Are the trust models “classical” and “pgp” as implemented in GNU PG > documented anywhere? The GNU Privacy Handbook has a good explanation of it: That is to say, it explains the Web of Trust. It doesn't

Re: Documentation of trust model

Hello, On 09/05/2017 12:58 AM, Mario Castelán Castro wrote: Are the trust models “classical” and “pgp” as implemented in GNU PG documented anywhere? As far as I know, not really. Certainly not in the OpenPGP RFCs. RFC4880 and its predecessors never defined any trust model, they only defined

Re: "Insecure memory" (yes setuid set) and "get_passphrase failed"

On Tue, 5 Sep 2017 02:45, marioxcc...@yandex.com said: > Are you sure that this is required in Solaris? At least in Debian > GNU/Linux there is no need to setuid the gpg binary to root. Root setuid > programs are a security problem. If an attacker can get control of this > program, he can

Re: "Insecure memory" (yes setuid set) and "get_passphrase failed"

Mario Castelán Castro wrote: > On 03/09/17 17:42, Dan Horne wrote: > > Warning: using insecure memory! > > gpg-agent[10073]: command get_passphrase failed: End of file > > gpg: problem with the agent: End of file > > gpg: Key generation canceled. > > There seems to be 2 different problems here: