nanog mailing list archives
Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx
From: Alex Rubenstein <alex () nac net>
Date: Fri, 26 Oct 2001 15:14:56 -0400 (Eastern Daylight Time)
I couldn't care less. And, I'm not saying it for affect. It's up to us to protect ourselves. On Fri, 26 Oct 2001, Dan Hollis wrote:
On Fri, 26 Oct 2001, Christopher Wawak wrote:Well, not exactly. Looking into the windows or checking the doorknobs is more akin to looking at your directory structre on your computer or file ... Scanning is more like going through the phone book or looking at the names on mailboxes in a neighborhood....So you dont mind if people portscan your network? -Dan -- [-] Omae no subete no kichi wa ore no mono da. [-]
Current thread:
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx, (continued)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Valdis . Kletnieks (Oct 26)
- RE: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Vivien M. (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Dan Hollis (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Alex Rubenstein (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Christopher A. Woodfield (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Alex Rubenstein (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Adam McKenna (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Dan Hollis (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Alex Rubenstein (Oct 26)
- Re: EXAMPLE: ### xxx Canada detected a penetration attempt from 209.123.x.229. Incident# xxxx Simon Lockhart (Oct 26)