[Feature request] send an user agent in hkp request

David Shaw dshaw at jabberwocky.com
Mon Feb 4 19:55:16 CET 2013

On Jan 30, 2013, at 4:56 PM, jbar <jeanjacquesbrucker at gmail.com> wrote:

> On Wed, 30 Jan 2013 17:04:27 +0100
> Werner Koch <wk at gnupg.org> wrote:
>> And before someone asks, we could of course add a --emit-full-version ;-)
> I don't consider softwares and versions as "private", but I agree with not sending such information, at least not needed, by default. And yes that could be great to have such option to enable such information in Armored data AND in the HTTP user agent. (i.e. with --armor AND with --recv-keys and --send-keys).
> Note: I don't want absolutely to have the GnuPG versions in HTTP user agent, I could also being satistfied to have only the default libcurl user-agent.

Note there is no default libcurl user-agent.  Or rather, the default libcurl user-agent is the empty string.  The curl command line tool has one, but programs that use the library are required to explicitly set one if they want it.

> The matter is that when you are a web admin, who checks the logs to detect eventual unexpected behaviours, empty HTTP user agent are always suspicious, and I prefer personnaly false, liar, or little wordy user-agents, than empty ones.

We've never had a user-agent for the HKP code in GnuPG.  If it was a problem, wouldn't it have come up before now?


More information about the Gnupg-devel mailing list