[plug] Blocking of Port 80

[Beau Kuiper]

Slashdot has beaten this one to death,

Basicly, people won't secure their machines, so ISPs block incoming port
80 requests to stop their customers machines being infected bythe red code
virus.

Since IInet wouldn't know what to do if their ass is on fire (I really
mean that), I assume they messed up blocking red code virus requests. I
would simply move your http server to another port, since getting them to
fix it would cause more grey hairs than you would want.

Beau Kuiper
kuiperba at cs.curtin.edu.au

On Tue, 14 Aug 2001, Craig Foster wrote:

> What do people make of the following e-mail I recieved from iiNet support
> after access to port 80 inbound refused to work? (HTTPS works sweet, HTTP
> connection timeout)
> I run a small dyndns.org machine so I can try out things like webmail, php,
> cgi, etc.
> I also know of a few people not with iiNet and some overseas who are having
> similar problems.
>
> ipchains input ACCEPT, output ACCEPT, forward MASQ (hey this e-mail had to
> get out somehow :-)
>
> Is this a little too helpful for an ISP, or are they just protecting the
> great unwashed?
>
> Regards,
>
> Craig Foster
>
>
>
> Sent Tue 14/08/2001 1:43 AM
>
>
> >Good Morning
>
> >At the moment I believe we are only filtering any http
> >requests that have the same characteristics as what the
> >code red was looking for. As far as I am aware, all other
> >http requests should work fine. Please let us know if
> >you are still having problems.
>
> >Kind Regards
> ><*name removed to protect the blameless*>
> >iiNet Support
>
>
>