sks-devel
[Top][All Lists]
Advanced

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

Re: SKS on alternate ports (was Re: [Sks-devel] diff logs not


From: Teun Nijssen
Subject: Re: SKS on alternate ports (was Re: [Sks-devel] diff logs not
Date: Sun, 17 Oct 2004 14:08:37 +0200
User-agent: Mozilla Thunderbird 0.8 (Windows/20040913)

Hi,

Yaron Minsky wrote on 2004-10-17 03:34:
On Sat, 16 Oct 2004 19:11:18 -0400, Jason Harris <address@hidden> wrote:

On Sat, Oct 16, 2004 at 06:31:58PM -0400, Yaron Minsky wrote:


to, since the actual keys are retrieved over the HTTP port.)  So this
should work fine for the case where mutliple SKS's are set up on the
same machine.

On the subject of port numbers:

In the SKS stats page, would it be possible to make "keyserver... 11370"
link to that stats page on each server?


Sadly, I don't think this is possible, at least not without some
mildly ugly hacks.  The problem is that SKS hosts only know each
other's reconciliation ports, not their HTTP ports.  And there's no
required relationship between the reconciliation ports and HTTP ports.
 You could guess, of course.  Or you could keep track of your gossip
partner's HTTP ports when you learn what they are during the course of
a reconciliation.  But all the options are either mildly hacky or
unreliable.

the obvious solution being to add the http port as an optional second port number in the membership file? e.g. replacing

skylane.kjsl.com 21370 # 2004-07-27 69.36.241.130 Jason Harris <address@hidden>

with

skylane.kjsl.com  21370 11371 # 2004-07-27

When people setup gossiping they know their ports reliably...

cheers,

teun

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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