Re: [Sks-devel] status page

[Tobias Frei]

Er, sorry, I see you already do that. Then maybe the automatic
detection failed for whatever reason.

And I just noticed that your status changed to "OK". Weird^^


Best regards,
Tobias Frei

Am 18.04.2014 13:30, schrieb Tobias Frei:
> Hi,
> 
> maybe you need to send a correct "Via:" header to allow automatic 
> detection of the reverse proxy. If proxying is done completely 
> transparent, there is probably no way to see that there is actually
> a proxy in front of sks. That's what I would assume, at least.
> 
> 
> Best regards, Tobias Frei
> 
> 
> Am 17.04.2014 16:20, schrieb Simon Lange (BIT):
>> well, but there IS a reverse proxy. ;)
>> 
>> tcp        0      0 78.46.21.218:11371      0.0.0.0:*
>>  LISTEN      8804/lighttpd tcp        0      0 127.0.0.1:11371
>> 0.0.0.0:* LISTEN      10018/sks tcp6       0      0
>> 2a01:4f8:201:22e3:11371 :::* LISTEN      8804/lighttpd
>> 
>> 
>> Am 2014-04-17 15:56, schrieb Tobias Frei:
>>> Hi,
>>> 
>>> from the status page you've linked:
>>> 
>>> "Latest status: Not OK Reason: Not running a reverse proxy"
>>> 
>>> 
>>> Best regards, Tobias Frei
>>> 
>>> Am 17.04.2014 01:13, schrieb Simon Lange:
>>>> Hi,
>>>> 
>>>> im a it supprised. i just stumbled over: 
>>>> https://sks-keyservers.net/status/info/keys.s-l-c.biz
>>>> 
>>>> which says that my keyserver was last seen three days ago. im
>>>> not enlisted anymore and the status page cannot even say what
>>>> server im running etc etc
>>>> 
>>>> im a bit wondered. why? i can reach it via 11370 11371 and
>>>> 443
>>>> 
>>>> proof? address@hidden:~$ gpg --keyserver
>>>> hkp://keys.s-l-c.biz --search-key address@hidden gpg:
>>>> searching for "address@hidden" from hkp server
>>>> keys.s-l-c.biz (1)     Simon Lange <address@hidden> 2048
>>>> bit RSA key BDD503BE, created: 2009-09-04 Keys 1-1 of 1 for
>>>> "address@hidden".  Enter number(s), N)ext, or Q)uit >
>>>> 
>>>> works like charme.
>>>> 
>>>> via browser? see attachment (screenshot). works too. ;)
>>>> 
>>>> recon works too 2014-04-17 01:12:04 Beginning recon as
>>>> server, client: <ADDR_INET [162.243.102.241]:59001>
>>>> 2014-04-17 01:12:04 Joining reconciliation 2014-04-17
>>>> 01:12:04 Reconciliation complete 2014-04-17 01:12:04 2 hashes
>>>> recovered from <ADDR_INET [162.243.102.241]:11371> 2014-04-17
>>>> 01:12:04 02D4107B2181C750E8EE7E18A96FBF61 2014-04-17
>>>> 01:12:04 1177F736C69004B45FA475ACB149F894 2014-04-17 01:12:04
>>>> Disabling gossip 2014-04-17 01:12:14 Requesting 2 missing
>>>> keys from <ADDR_INET [162.243.102.241]:11371>, starting with 
>>>> 02D4107B2181C750E8EE7E18A96FBF61 2014-04-17 01:12:14 2 keys 
>>>> received
>>>> 
>>>> 
>>>> so why is my server not enlisted anymore? what are the
>>>> exactly port protocols you are checking?!
>>>> 
>>>> id like to prevent such a status page although keyserver is
>>>> still up n running. oO
>>>> 
>>>> thanks for your help
>>>> 
>>>> Simon
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________ Sks-devel
>>>> mailing list address@hidden 
>>>> https://lists.nongnu.org/mailman/listinfo/sks-devel
>>>> 
>>> 
>>> 
>>> _______________________________________________ Sks-devel
>>> mailing list address@hidden 
>>> https://lists.nongnu.org/mailman/listinfo/sks-devel
>> 
> 
> 
> 
> _______________________________________________ Sks-devel mailing
> list address@hidden 
> https://lists.nongnu.org/mailman/listinfo/sks-devel
>

smime.p7s
Description: S/MIME Cryptographic Signature