sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Ports used by sks


From: Andy Ruddock
Subject: Re: [Sks-devel] Ports used by sks
Date: Tue, 03 Feb 2009 08:00:03 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12 (Ubuntu-1.1.12+nobinonly-0ubuntu1)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Shaw wrote:
> On Feb 2, 2009, at 7:30 PM, Christoph Anton Mitterer wrote:
> 
>>> Also, isn't the port changeable on a per-peer basis in SKS?  If so,
>>> there is no point in registering the port at all, as setting up a new
>>> peer is a manual operation.
>>
>> Well but this is also the case with the 11371 port, and basically with
>> most other protocols, too, isn't it?
> 
> No, the 11371 port is needed because it is part of the HKP protocol,
> just like 80 is part of the HTTP protocol.  11370, on the other hand, is
> just some port that SKS uses.  It's not in use by clients.  That port is
> manually configured.

Isn't port 80 simply the default port used by http, certainly it's not
uncommon to use other ports (8080 springing to mind).
The http spec (rfc2616) says:
"The default port is TCP 80 [19], but other ports can be used."
[19] is a pointer to rfc1700 - assigned numbers.

- --
Andy Ruddock
- ------------
address@hidden (GPG Key ID 0xA622D452)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmH62wACgkQfSkWkaYi1FJP9gCfXkNBm2tikNBaxbfPn3MLrMKt
/40An2JXYmZ4wTxwPaDMU3NuUCiEvxvR
=zMPZ
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]