Re: weird scans from port 80
From: Bill K. (bilkay@xxxlocalnet.com)
Date: 01/20/03
- Next message: Tim Haynes: "Re: weird scans from port 80"
- Previous message: Julian Holley: "Re: How generate my own access log ?"
- In reply to: Kasper Dupont: "Re: weird scans from port 80"
- Next in thread: Tim Haynes: "Re: weird scans from port 80"
- Reply: Tim Haynes: "Re: weird scans from port 80"
- Reply: Silviu Minut: "Re: weird scans from port 80"
- Reply: Kasper Dupont: "Re: weird scans from port 80"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Bill K." <bilkay@xxxlocalnet.com> Date: Mon, 20 Jan 2003 13:33:06 GMT
In article <3E2ACF08.D4978104@daimi.au.dk>, "Kasper Dupont"
<kasperd@daimi.au.dk> wrote:
> From RFC 793 page 36:
>
> As a general rule, reset (RST) must be sent whenever a segment arrives
> which apparently is not intended for the current connection.
The next sentence reads: "A reset must not be sent if it is not clear that this is the
case."
Why did you snip it?
Sorry for butting in.
- Next message: Tim Haynes: "Re: weird scans from port 80"
- Previous message: Julian Holley: "Re: How generate my own access log ?"
- In reply to: Kasper Dupont: "Re: weird scans from port 80"
- Next in thread: Tim Haynes: "Re: weird scans from port 80"
- Reply: Tim Haynes: "Re: weird scans from port 80"
- Reply: Silviu Minut: "Re: weird scans from port 80"
- Reply: Kasper Dupont: "Re: weird scans from port 80"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|