[Sks-devel] Now what'd I break

[Chris Kuethe]

It looks like something in my database may be a bit munged; querying for
my key doesn't show my the names of my signers, and I get this in the log:

http://pgp.cns.ualberta.ca:11371/pks/lookup?search=ckuethe&hash=on&op=vindex

2004-01-28 08:21:21 Get request received
2004-01-28 08:21:21 <ADDR_INET 24.67.136.130:58822> => 
/pks/lookup?search=ckuethe&hash=on&op=vindex
2004-01-28 08:21:21 /pks/lookup: Index request: (ckuethe)
2004-01-28 08:21:21 Unable to print key from query 'ckuethe': 
KeyMerge.Unparseable_packet_sequence


Whereas I get the expected results for this query from sks.dnsalias.net.

Actually, I'm seeing quite a lot of stuff like this:

2004-01-26 21:35:09 /pks/lookup: Index request: (0x2428f5758443c2b2)
2004-01-26 21:35:09 Unable to print key from query '0x2428f5758443c2b2': KeyMerg
e.Unparseable_packet_sequence
...
2004-01-26 21:45:14 Error fetching key from hash 03DF058ADE43F87A327C648A9D01777
7: Not_found
2004-01-26 21:45:14 Error fetching key from hash 03E44AE69040B5E27251E928B49CAC8
8: Not_found

My syncs claim to be working correctly now; hashes show up in the diff files
and then a in the database. I've already run cleandb and update_subkeys, and
this did not help. I'm thinking it was something about the keydump I loaded
(from rediris.es). Shouldn't SKS be able to sync every last hash, key and
metadata object? I did make sure to keep my database completely quiescent
while loading keys...

Also, I've tried dropping the key, but that doesn't seem to work either. I
either get a complaint about the hash being too short or that I must specify
only one key; this sounds like a problem parsing argv[]... can anyone else
use drop successfully?

CK

-- 
Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
      office: 157 General Services Bldg.    +1.780.492.8135
              address@hidden

     GDB has a 'break' feature; why doesn't it have 'fix' too?