full-disclosure - RE: MS SQL WORM IS DESTROYING INTERNET BLOCK PORT 1434!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1043560171.19604.83.camel@liberate.anize.org>
From: douglist at anize.org (Douglas F. Calvert)
Subject: RE: MS SQL WORM IS DESTROYING INTERNET BLOCK
	PORT 1434!

On Sat, 2003-01-25 at 21:05, Benjamin Krueger wrote:
> * Jason Coombs (jasonc@...ence.org) [030125 16:49]:
> > Bank of America should never have allowed their ATM network to rely on
> > routes that could be impacted by non-ATM network computer systems.
> > 
> 
> It's a little early to be assuming that the ATMs were gummed up by
> network route congestion, isn't it? I find it entirely possible that
> their datacenter where the transactions are processed was the real
> scene of the outage, and not the individual ATMs or their routes.

Who cares about the exact reason, the problem is that critical banking
infrastructure was damaged because of an internet slowdown. Why is it
better that a banking "datacenter's" integrity was compromised than
network route congestion. If I had to pick between two banks each
exhibiting these problems I'll take one that is only affected due to
network congestion in ATM traffic than one that has it's entire
datacenter f*cked by a worm...

-- 
Douglas F. Calvert <douglist@...ze.org>