Re: scanning my ports

1999-09-26 Thread Jason Gunthorpe
On 26 Sep 1999, Mark W. Eichin wrote: > In addition to apologies to Mr. Norman, perhaps there's some value in > either (1) making tcplogd etc. require enough configuration to force > people to read the documentation, or (2) enhance those packages to > interpret things a little more, so they scare

Re: scanning my ports

1999-09-26 Thread Nathan E Norman
On 26 Sep 1999, Mark W. Eichin wrote: : In addition to apologies to Mr. Norman, perhaps there's some value in : either (1) making tcplogd etc. require enough configuration to force : people to read the documentation, or (2) enhance those packages to : interpret things a little more, so they sc

Re: scanning my ports

1999-09-26 Thread Mark W. Eichin
In addition to apologies to Mr. Norman, perhaps there's some value in either (1) making tcplogd etc. require enough configuration to force people to read the documentation, or (2) enhance those packages to interpret things a little more, so they scare naive users a bit less?

Re: scanning my ports

1999-09-25 Thread John Lapeyre
*Nathan E Norman wrote: > Mr. Lapeyre, > > You do realise that pavlov.midco.net is part of the DNS rotation > http.us.debian.org? No, I didn't. I was using the mirror. I am in error. Obviously the connections to several ports on my machine were a legitmate part of the transfer of data to my

Re: scanning my ports

1999-09-25 Thread Nathan E Norman
-BEGIN PGP SIGNED MESSAGE- On Fri, 24 Sep 1999, John Lapeyre wrote: : Dear Security Staff: :I received 2086 connection attempts at several ports on September 22. : The attempts were made from IP address pavlov.midco.net [24.220.0.13] : The machine whose ports