Am Fri, 8 Apr 2016 09:04:31 +0100 schrieb Chris Boot <[email protected]>: > > So what is the best practice here? I found some sks servers running > > the same web-pages on 11371 and some which do not provide any > > webpage. > > > That's fair enough - I don't use nginx for my keyserver so I can't > really comment on those instructions, but it feels to me like a > keyserver should present the same interface on port 11371 as it does > on port 80. That's not to say that it's broken, and it certainly > looks like it will work for the more general use case of GPG fetching > keys, it just feels less user friendly.
I with you regarding the user friendliness. So let me see if I should simply get rid of nginx or find another solution to provide the WebUI also on Port 11371. :-) > Yes, you only need the outgoing part, and certainly no harm asking > Jonathan about it first. ok. > The problem, as I understand it, is that SKS servers will only > mailsync changes pushed directly to them and not changes gossiped > from other SKS peers. That means that servers that rely on mailsync > alone will be missing out on a large proportion of changes from the > keyserver network. That's bad. But I guess nothing we can fix here other than providing the Email interface to the PKS servers - which I did now. > With all that said, I've added you to my membership file. Please add > me in return: > > sks.bootc.eu 11370 # Chris Boot <[email protected]> 0xF5C83C05D9CEEEEE Thank you - and again thanks for your explanations and suggestions! => added your server to the membership file. With kind regards, Lars
pgpWl4UgOyBA2.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ Sks-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/sks-devel
