Checking key server response against the request parameters
Stefan Tomanek
tomanek at internet-sicherheit.de
Sat Oct 5 12:34:30 CEST 2013
Hello,
Dies schrieb Werner Koch (wk at gnupg.org):
> > I just noticed that gnupg will even import secret keys from any keyserver
> > response if the key data is prefixed with "BEGIN PGP PUBLIC KEY DATA".
>
> That is correct. It will do so even for keys retrieved via DNS. I have
> a pretty simple patch against this in the queue.
With that sorted out, did you find the time to look over my patch regarding the
matching of keyserver responses to their request parameters?
Sincerly
Stefan Tomanek
--
if(is) - Institut für Internet-Sicherheit
Westfälische Hochschule, Gelsenkirchen
OpenPGP-Schlüsselkennung: 0x2788CD17B78FEAFA
OpenPGP-Fingerabdruck: 15F9 00BF BA9B 685D 15D0 266C 2788 CD17 B78F EAFA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: </pipermail/attachments/20131005/cc348ebf/attachment.sig>
More information about the Gnupg-devel
mailing list