Re: [Sks-devel] Strange SKS traffic

[Kim Minh Kaplan]

Arnold writes:

> Hello,
>
> Since Tue Oct 26, my firewall blocks some strange outgoing traffic. It
> turned out to be SKS data I try to send to keyserver.gingerbear.net at
> destination port _2_1371.
>
> I do not understand why my server tries to contact gingerbear at that
> special port, as it is listed in my membership file with the normal 11370.
> While examining the stats, I found gingerbear has a gossip peer 'basket'
> that is configured at port 21370. Now it seems to me that the configuration
> data of gingerbear for basket somehow 'leaks' to my system. That, in turn,
> makes my system try to use that port 21371 (for basket) while communicating
> with gingerbear.
>
> Can somebody explain why this happens?

I have seen this happen too.  The peer recon process tells your server
on which port the DB process listens so it is normal that if one of your
peers tells your recon process to fetch keys using port 21371 it does
so.
-- 
Kim Minh