defining port number for keyserver searches
jesse200808+gpg-users at gmail.com
Tue Jun 30 08:19:55 CEST 2009
Does gpg use bind(2) at all? I guess when retrieving keys it only uses
connect(), so there shouldn't be a problem with NAT and inbound
connections and stuffs...
On Mon, Jun 29, 2009 at 9:26 PM, Malte Gell<malte.gell at gmx.de> wrote:
> David Shaw <dshaw at jabberwocky.com> wrote
>> On Jun 29, 2009, at 8:43 AM, Malte Gell wrote:
>> > I would like to define a fixed port number (the same 11371) for gpg
>> > which waits
>> > for the answer from the keyserver. Can I tell gpg at which port to
>> > listen?
>> If I understand your question, you're trying to set the *local* port
>> number that GPG uses when binding the socket to talk to a keyserver?
> Yep. My machine is connected to a router that blocks incoming traffic. If I
> could assign a fixed port for gpg --search-key I could open this port for
> incoming traffic. At the moment gpg uses a different port each time i use gpg --
> search-key for incoming traffic and so i cant specify a rule.
> The funny thing I dont understand, when surfing the web, Firefox of course also
> uses high ports for receiving data and these don't get blocked...(which is not
> desired of course)
More information about the Gnupg-users