Re: [Sks-devel] Persistent differences with sks.keyserver.penguin.de

[Teun Nijssen]

Hi Yaron,

(Jan Kesten en Darryl Ross, please read)

I'll bite the bullet; my situation at the SURFnet server is much worse.
I haven't had time to look into it, and my server and bandwidth are 
large enough not to be too worried, but....

I am running self compiled (sorry Peter) SKS 1.0.9 without any 
additional patches on a dedicated Debian (sarge) machine; in the times 
of SKS 1.0.8 on Debian (woody) my situation was the same.

on 25-11-04 04:33 Yaron Minsky said the following:
> I've noticed an interesting issue looking at the reconciliation logs. 
> in particular, it appears that there is a persistent difference
> between sks.keyserver.penguin.de and my computer.  This sequence comes
> up over and over:

> 2004-11-24 22:25:31 Disabling gossip
> 2004-11-24 22:25:32 Requesting 1 missing keys from <ADDR_INET
> 134.169.171.249:11371>, starting with E66B638A693C095062EA8EC1F24FCDA9
> 2004-11-24 22:25:32 0 keys received
> 2004-11-24 22:25:32 Enabling gossip
>
> As you can see, the key can't actually be retrieved.  I suspect that
> this is because there is an inconsistency between that server's ptree
> database and its key database.  Bjoern, could you try and recreate
> your ptree database and see if this problem goes away.  I'm generally
> quite curious how this siutation can come to be.

My gossip membership list has 11 entries. All of them actually gossip, 
given the times (I type this at 09:29) in:
-rw-r--r--  1 sks  sks        627 Nov 25 09:22 diff-129.128.98.22_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 08:45 diff-161.53.2.67_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:19 diff-193.174.13.74_11371.txt
-rw-r--r--  1 sks  sks      37191 Nov 25 09:13 diff-202.191.97.141_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:23 
diff-212.242.141.114_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:08 diff-213.141.74.169_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:26 
diff-213.146.108.162_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:11 diff-62.116.124.106_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:09 diff-66.119.199.39_11371.txt
-rw-r--r--  1 sks  sks          0 Nov 25 09:22 diff-69.36.241.130_21371.txt
-rw-r--r--  1 sks  sks       2112 Nov 25 09:20 diff-81.169.179.29_11371.txt

Given the number of partners that have zero keys exchanged I think my 
database is up to date and gossip works with at least the majority of 
partners.

Note that 81.169.179.29 which is
gpg-keyserver.de 11370 # 2004-07-30 81.169.179.29 Jan Kesten
and 202.191.97.141 which is
keyserver.afoyi.com 11370 # 2004-10-30 202.191.97.141 Darryl Ross
tell me about 64 and 1127 keys. For a long time already.....

address@hidden:~$ wc -l /var/sks/diff*.txt
   19 /var/sks/diff-129.128.98.22_11371.txt
    0 /var/sks/diff-161.53.2.67_11371.txt
    0 /var/sks/diff-193.174.13.74_11371.txt
 1127 /var/sks/diff-202.191.97.141_11371.txt
    0 /var/sks/diff-212.242.141.114_11371.txt
    0 /var/sks/diff-213.141.74.169_11371.txt
    0 /var/sks/diff-213.146.108.162_11371.txt
    0 /var/sks/diff-62.116.124.106_11371.txt
    0 /var/sks/diff-66.119.199.39_11371.txt
    0 /var/sks/diff-69.36.241.130_21371.txt
   64 /var/sks/diff-81.169.179.29_11371.txt

In my case, keys *are* retrieved (the same ones time and again) and 
added to my database, none getting past the filters, so the gossip 
partners remain different indefinitely.

Merging the output of two log files I see things like
tail -f /var/sks/log.db    &
tail -f /var/sks/log.recon &

2004-11-25 09:40:43 Beginning recon as server, client: <ADDR_INET 
202.191.97.141:33832>
2004-11-25 09:40:43 Joining reconciliation
2004-11-25 09:40:54 Reconciliation complete
2004-11-25 09:40:54 1127 hashes recovered from <ADDR_INET 
202.191.97.141:11371>
2004-11-25 09:40:54 Disabling gossip
2004-11-25 09:40:56 Handling /pks/hashquery
2004-11-25 09:40:56 1 keys found
2004-11-25 09:41:01 Reconciliation attempt from <ADDR_INET 
69.36.241.130:2366> while gossip disabled. Ignoring.
2004-11-25 09:41:04 Get request: <ADDR_INET 80.202.101.169:25597> => 
/pks/lookup?op=index&search=jesro
2004-11-25 09:41:04 /pks/lookup: Index request: (jesro)
2004-11-25 09:41:04 Requesting 100 missing keys from <ADDR_INET 
202.191.97.141:11371>, starting with 009F5DF8E8688278919CCF879B864F03
2004-11-25 09:41:06 1 potential merges found for keyid F59C9BDB
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 1 potential merges found for keyid 81F1CD76
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 1 potential merges found for keyid 59F55C2F
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 1 potential merges found for keyid AC675972
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 1 potential merges found for keyid B56DA72F

<omitted more lines>

2004-11-25 09:41:06 1 potential merges found for keyid F2FE289E
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 1 potential merges found for keyid 9DDB7C36
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 1 potential merges found for keyid ED695653
2004-11-25 09:41:06 2 updates found before filtering
2004-11-25 09:41:06 Applying 0 changes
2004-11-25 09:41:06 100 keys received
2004-11-25 09:41:09 Requesting 100 missing keys from <ADDR_INET 
202.191.97.141:11371>, starting with 18665485D56F3D817B2774C86437C3C2
2004-11-25 09:41:12 1 potential merges found for keyid 3CFC701B
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 326AC092
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 708AB8C2
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 8439C417

<omitted more lines>

2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 16D79E96
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 2970EC52
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid D1A2306E
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 2BF8EBEE
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 1 potential merges found for keyid 34C5FFDA
2004-11-25 09:41:12 2 updates found before filtering
2004-11-25 09:41:12 Applying 0 changes
2004-11-25 09:41:12 Adding list of 1 keys from file 
/var/sks//var/sks/messages/msg-04719212.ready
2004-11-25 09:41:12 0 potential merges found for keyid 5DB7F522
2004-11-25 09:41:12 1 updates found before filtering
2004-11-25 09:41:12 Applying 1 changes
2004-11-25 09:41:12 Adding hash 136E03C62EF9B07B5A7BA975309D647C
2004-11-25 09:41:12 Adding list of 1 keys from file 
/var/sks//var/sks/messages/msg-65093496.ready
2004-11-25 09:41:12 Applying 0 changes
2004-11-25 09:41:12 100 keys received
2004-11-25 09:41:15 Sending LogResp size 1
2004-11-25 09:41:15 Not gossiping because gossip is disabled
2004-11-25 09:41:15 setting synctime to 1101372072.839737
2004-11-25 09:41:15 Added 1 hash-updates. Caught up to 1101372072.839737
2004-11-25 09:41:15 Requesting 100 missing keys from <ADDR_INET 
202.191.97.141:11371>, starting with 3191EE143E8047710DA0045BA69F5A90
toff
Killed tail(28771) with signal 15
Killed tail(28772) with signal 15
address@hidden:~$

I think at least Darryl built/compiled SKS recently, so why does his 
machine contain keys that are filtered on mine?

cheers,

teun

signature.asc
Description: OpenPGP digital signature