Hi Kristian, > The workaround is to make SKS listen to e.g. port 11372, as specified > in hkp_port in sksconf, that is allowed access only by your peer list.
That's an interesting idea as a workaround as ngnix would not protect sks... I'll think about that. > As for the use of nginx, are you sure this is being done on the > public-facing interface? try running e.g. "wget -S > http://keyserver.ccc-hanau.de:11371/pks/lookup?op=stats"; , at the > moment I'm only seeing "Server: sks_www/1.1.1" from my computers. Ah, now I see the reason: That's because I just configured it for IPv4, but not for IPv6! Thank you :) Regards, Jens _______________________________________________ Sks-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/sks-devel
