Re: [Sks-devel] 1.0.8 release candidate

[Yaron Minsky]

Indeed, they are not fixed, largely because I did not know about them
until now.  I think 1.0.8 will probably be released without these
changes, since I've just spent a bunch of time hacking, and can't make
more right now unless it's quite urgent.

That said, if someone submits patches for these issues in the next few
days, I would be happy to include them in the final 1.0.8 release. 
The changes should be pretty simple to do.

y


On Mon, 04 Oct 2004 15:26:34 +0200, Reimer Karlsen, DFN-CERT
<address@hidden> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Hi Yaron,
> 
> as I read that there will be some new release of SKS I wonder if the three
> following things will be fixed the new release:
> 
> 1. When requesting
> 
> http://pgpkeys.pca.dfn.de:11371/pks/lookup?op=index&search=fhg.de
> 
> SKS returns a 500 HTTP error and a notice about an exception.
> 
> In this case PKS returns a 200 and some humanreadable information about too
> many returned key matches:
> 
> ~ Public Key Server -- Error
> 
> ~ Number of keys in reply (544) exceeded maximum allowed (500) Try a more
> ~ specific query.
> 
> 2. and 3. When requesting specificly a key id starting the search string
> with 0x SKS thoughs an ugly exception when the actual keyid is not a valid
> hex string.
> 
> If PKS is asked
> 
> http://blackhole.pca.dfn.de:11371/pks/lookup?op=index&search=0xkarlsen
> 
> it returns a 200 HTTP error code and the following message:
> 
> ~ Public Key Server -- Error
> 
> ~ Key ID string should be 8, 16, or 40 characters long
> 
> If PKS is asked
> 
> http://blackhole.pca.dfn.de:11371/pks/lookup?op=index&search=0xkarlsena
> 
> it returns a 200 HTTP error code and the following message:
> 
> ~ Public Key Server -- Error
> 
> ~ Key ID must contain only hexadecimal digits
> 
> ~From the attached changelog in your mail I can't figure out if these things
> are already fixed.
> 
> Cheers
> 
> Reimer
> 
> Yaron Minsky wrote:
> | I've bumped the version number of the latest TLA revision as 1.0.8.
> | Consider this a release candidate.  If nothing awful comes up in the
> | next week, I'll upload a tarball to the website.  Below is the full
> | changelog.  The last set of changes is just fixes to how the logging
> | is currently done, the goal of which is to make the logging
> | improvements being worked on by others easier to do.
> - --
> Dipl. Inform. Reimer Karlsen (PKI Team), DFN-CERT Services GmbH
> https://www.dfn-cert.de, +49 40 808077-615 / +49 40 808077-555 (Hotline)
> PGP RSA/2048, 1A9E4B95, A6 9E 4F AF F6 C7 2C B8  DA 72 F4 5E B4 A4 F0 66
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iQEVAwUBQWFPhhKWILoankuVAQE0TwgAsMXjAS0Xv1zpoHF9BcXwXeX74RRkCAPP
> Hmx+z/g7qIdRu/J4GEAHz9sXfWdxVhBZm1SToBRMXypZsswusK0fMQFmfLhaN7ze
> WgGxjjgkFbq8e/lHQQDIH/PHXNa4gUZ0/kVjo5SKPj6QTW3/vxGNhfjJrEcaFFoQ
> asHVvRuaJXsSh2FyYY0vw0hDM99QpSf/QDO2sM98qu4qenMpnSL9d1MpmjaWkxSO
> TjgL42MdP9JTh2Ca2hBKT5k+jzKTP0BNEOXWtmsbrgcL5GDKXA1E/FKIRyCeIyAb
> mKLdPg0UhT9SnIlkDsHSrNLafbyKV2FttigoE3koUIfB2kNW9vInww==
> =hbbG
> -----END PGP SIGNATURE-----
>