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
| ||
|
Message-ID: <012001c415ce$bf8b24f0$4df24243@tsgincorporated.com> From: micheal at tsgincorporated.com (Micheal Patterson) Subject: Re: Addressing Cisco Security Issues ----- Original Message ----- From: "Jason Dodson" <mindchild@...oo.com> To: "Geo." <geoincident1@...info.org>; <full-disclosure@...ts.netsys.com>; <bugtraq@...urityfocus.com> Sent: Monday, March 29, 2004 1:35 PM Subject: Re: Addressing Cisco Security Issues > I have had a similar run-around with AT&T Broadband and Sprint a while back, pertaining to a DoS > attack my organization was experiencing. Not to dive into details, to resolve the issue, I got > them both on the line in a 3-way conversation, and it was taken care of in less then 5 minutes. > They didn't seem to eager to shrug off the responsibility to someone else, when that someone else > was right there on the phone. > > Jason Dodson > I've had similar situations between former Brooks Telecom (now WorldComm/MCI) and SBC for pri and DS3 circuit issues. Once I was able to get both NOC's on the line, they couldn't point the blame at anyone else. When one side would try, the other would say, well, no it can't be that because of ... and they started working together to get the problem resolved. When you're on the line with only one party, it's easy for them to point to the distant end as a problem. -- Micheal Patterson TSG Network Administration 405-917-0600 Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Powered by blists - more mailing lists