sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] [GnuPG-users] sks-keyservers.net: Changes to pools / SRV


From: Kristian Fiskerstrand
Subject: Re: [Sks-devel] [GnuPG-users] sks-keyservers.net: Changes to pools / SRV Weights
Date: Sun, 13 May 2012 18:09:31 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2012-05-13 17:43, Giovanni Mascellani wrote:
> Hi.
> 
> Il 13/05/2012 16:41, Gabor Kiss ha scritto:
>> OK. I understand the situation. Sksconf and peer's membership 
>> files must contain the _same_ name whatever it is. In this case 
>> Giovanni must decide what name to use.
> 
> I changed the hostname in the configuration, although I find it a 
> rather funny requirement.
> 
> 

Thanks Giovanni,

Its not really a "requirement" per se, the only requirement is that
the hostname specified is a FQDN that is accessible, as Jeff puts it
in [0] "Perfect: from this (and other remarks) and other comments
your definition of "proper FQDN" policy can be inferred (afaict):

        The hostname reported in sksconf needs to be a "proper FQDN"."

This is because it is used as the identifier, and will be what is
shown in the status page of the pool[1] at any given time, in order
for it not to be duplicates there.

But to properly show the peer mesh in e.g. [2], which isn't really
being used for anything by me (read, the pool), it holds true that the
membership entry and sksconf entry has to be the same.

[0] http://lists.nongnu.org/archive/html/sks-devel/2012-04/msg00098.html
[1] http://sks-keyservers.net/status/
[2] http://sks-keyservers.net/status/info/keys.niif.hu



- -- 
- ----------------------------
Kristian Fiskerstrand
http://www.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Corruptissima re publica plurimæ leges
The greater the degeneration of the republic, the more of its laws
- ----------------------------
This email was digitally signed using the OpenPGP
standard. If you want to read more about this
The book: Sending Emails - The Safe Way: An
introduction to OpenPGP security is now
available in both Amazon Kindle and Paperback
format at
http://www.amazon.com/dp/B006RSG1S4/
- ----------------------------
Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPr9y7AAoJEBbgz41rC5UICjgP/Aje4jJrl5ed5gzalZ9bWA9v
PU9bvaxsavtgFzdodj0j7WvkK6JPNi2u53qM0VxjRfCTzNfrcpNPdxR220Hgf6b+
h9jRJInw8Vy9bJSHca+AAKNULgg1/ZEaot6eiK/ycX26pgcBRpacPgJGiv/HaLs3
sGpDjsdF2B7O6YtzLui7DeckgIH4vxZ7b+9zlNt1xYOHRM2OcDdnqoeMQN/tYdNi
omszrN2BltaUSTtKRU1bpL5LAksv5ShRxV9XO3gwLXde2ixsG3eiikzmQlJiitXq
YBMyGsi38E6s0fKi4DlLHXqCIoEM7Rv+uC4S6kNTziZa/lW8G4p3qBQGN7LvJdYR
cz5nG4A9tYuG+z3ywAjSZxOKoqkAU1s0drk5uSmP8B7FxZHvKJfRXtAfp9MA7b5f
i3vYyhv3yyyjMVwXoDpvbxp1Ve5guT9ZM8OS1VtjZcRBneL+nOztqMUG0m5yOKOP
kGr2fB9SwNEgFRC3Lj+/SSn0hs1em17RCxAOyw2isBhbk1aX8Sm13QIYPMy7WyGl
otrZngbHXkR94q0ZotzSVc6HBXtFY/fvDNyyxf6RJ6/owBQDT0LJ/hXupO37cA2+
RFAfAJJJQOuEJVOFumHfFRveq4pKIr8L122tUbj/9WO4Y0oYs2ihy48KA6o/tRTE
5Q+39Rt9gZ6+MJXmnynp
=mrHV
-----END PGP SIGNATURE-----




reply via email to

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