-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 22 September 2001 02:12 pm, Michael Stack wrote:
> Apparently, some ISPs are actually shutting down user's accounts
> until they patch their machines.
>
>
> http://www.wired.com/news/business/0,1367,47037,00.html
Thanks for the link, good to see some ISP's reacting. However, shutting
down access for those machines won't get them patched, as they'll have
no way to download the patches. Of course, since patches available for
many months hadn't been applied yet, there is a good argument for
keeping them disconnected. ;)
What I did find interesting is the number of ISP's who have emailed all
subscribers, telling them about the problem, and how to patch their
systems.
I use charter cable. They have never contacted users about this, code
red, or any other exploit. When code red hit, I began running a script
to parse the logs and create a list of infected machines. Most of the
recent code red hits are still originating from machines on the charter
network. Charter's response to this newest exploit was to shutdown all
port 80 inbound traffic, without telling anyone. While that will help
with bandwidth issues inside the router, it isn't going to do anything
about cleaning up infected machines.
Hrmm, that turned into an almost anti charter rant. I think I have a
customer support phone call to make. :)
- -D
- --
pgp key: http://www.tuxfan.homeip.net:8080/pgpkey.txt
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7rQFMeMAUbzJhSVcRAqOOAJ0c+aARzYiVUOMYF7KmW/5T54Ew1wCfbwr8
0Q57s9KnwRwRuhYGsvAmpbY=
=aiq9
-----END PGP SIGNATURE-----
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
