July 2001 - Test - lists.nanog.org

RE: Cisco IOS Vulnerability
by Vandy Hamidi 02 Jul '01

02 Jul '01

Does this vulnerability affect CatOS as well? I was under the impression it was just IOS devices. -=Vandy=- -----Original Message----- From: up(a)3.am [mailto:up@3.am] Sent: Friday, June 29, 2001 6:03 PM To: Larry Diffey Cc: nanog(a)merit.edu Subject: Re: Cisco IOS Vulnerability On Fri, 29 Jun 2001, Larry Diffey wrote: > CERT and Cisco have issued a warning about a vulnerability in the > Cisco IOS starting at version 11.3 and affecting all later versions. > > If your Cisco equipment is HTTP enabled and you're not using TACACS+ > or RADIUS for authentication it is vulnerable to complete takeover. > The hack is very simple. Yeah, well who enables httpd on their Ciscos, anyway? Wait a sec, the Catalysts have this enabled by default... James Smallacombe PlantageNet, Inc. CEO and Janitor up(a)3.am http://3.am =========================================================================

1 0

VPN Migration
by Troy Corbin 02 Jul '01

02 Jul '01

im looking for any operational experiences/references regarding large wan migrations from private frame-relay to extranet VPNs for remote office connectivity. specifically, what backbone provider(s) did you choose, what type of cost savings were realized in both telco charges as well as management overhead, and what performance increases/decreases did you experience? thanks, troy

1 0

Re: So.. you want to track some DoS traffic?
by Christopher L. Morrow 02 Jul '01

02 Jul '01

On Mon, 2 Jul 2001, Alex Bligh wrote: > > Credit: Credit should go to those listed in the link, UUNET's TAC-Eng > > group, UUNET's Net-Sec group, UUNET's Customer Router Security Group, > > dies(a)pulltheplug.com and a few others I have forgotten. > > Slight sense of Deja Vu. > > Without wishing to blow my own trumpet, from NANOG in 1999: > > http://answerpointe.cctec.com/maillists/nanog/historical/9907/msg00083.html So basically you've proposed implementing black hole routing via a community... this is nice and COULD be used by customers, though I'd be worried about them blackholing something 'important' and not figuring it out... which is all too common a problem. We discussed this at implementation/design time and fell back on "we would rather do it manually, just in case...". Additionally, if someone messed up the customer's filter and didn't filter their routes they could accidently drop traffic another customer :( Manual and by a select few people was the end decision. Not that it's not a great idea, but BGP is 'hard' and customers (and providers) routinely screw it up :( Also, your paper doesn't hit the main thing I was getting at: Tracking the attack... dropping traffic is great and you can do it in 101 different ways, but the tough part was tracking it... (at least it was the tough thing we was trying to make less tough). -Chris

1 0

Re: Common causes of performance problems and outages
by Jeff Weisberg 02 Jul '01

02 Jul '01

| I want to find out the most common causes of | performance problems as well as outages in | networks today. Any information is welcome! - The customer - A vendor - Another 3rd party - Came clear during testing --jeff

1 0

More on SBC's new DSL contracts...
by Christopher A. Woodfield 02 Jul '01

02 Jul '01

...and what they intend to do with them. http://news.cnet.com/news/0-1004-200-6442646.html?tag=tp_pr -C --------------------------- Christopher A. Woodfield rekoil(a)semihuman.com PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B

1 0

ISP contracts and government intervention
by ethanpreston＠hushmail.com 02 Jul '01

02 Jul '01

Apologies in advance for the non-technical nature of the query. I am a law student researching a law review article on censorship on the Internet. My partner and I are investigating the legal consequences of placing a ISP offshore, in a jurisdiction like Anguilla, Nevis, the Caymen Islands or some other place like that. Part of our problem is that we're ignorant of the business practice in the area. I figured I'd go to the horse's mouth, rather than playing footsie on the legal lists. Its probable that the ISP could be run in an offshore jursidiction with strong financial secrecy regulations and any U.S.-based managers/owners would be insulated from legal action because they could not be identified (at least, with American subponeas.) On the other hand, a U.S. judge could presumably order the offshore ISP's U.S.-based upstream ISP to cut off that ISP (or even the entire jurisdiction, depending on the situation) for DMCA violations, gambling, etc. Basically, its an issue of how the community would go about dealing with a blackhat ISP. An initial question is how closely do backbone providers/upstream ISPs look at offshore ISPs to begin with? What kind of identification/credentials does an ISP need to come up with to get a contract? Specifically, do backbone providers figure out who the beneficial owner of an ISP is before they hook up the ISP? If someone pays the bills regularly, do they need anything more than what's in whois.arin.net? The next set of questions deal with how long a blackhat ISP could stay connected. Under what circumstances would an upstream ISP/backbone provider cut off the offshore ISP before a court order? What are the choices in the market for backbone providers that are not U.S.-based (and therefore wouldn't be subject to U.S. legal process)? Free, encrypted, secure Web-based email at www.hushmail.com

6 7

RE: GRC rides again...
by Roeland Meyer 02 Jul '01

02 Jul '01

> From: David Howe [mailto:DaveHowe@gmx.co.uk] > Sent: Monday, July 02, 2001 2:48 AM > > ... With yet another "update" to the DDos pages. > http://grc.com/dos/intro.htm > and I quote: > > Unfortunately, today we see only the operation of blind > self-interest from > > Microsoft and the Internet's ISP's > > As I seem to recall several members of this list offered him > help (and were rebuffed) perhaps they > would like to comment? He seems increasingly lost in > a fantasy world where everyone is out to get him.... The question I have is, would QoS would do any good here? Other then that, he seems to be on a rant here. As much as I hate to say it, I almost agree with MSFT here. That said, Novell stated, decades ago, that MSFT never could understand network security. At the time, I agreed with Novell. Current observation is, that MSFT has yet to learn. Considering MSFT's workstation market-share, that is a problem for all of us.

5 4

Re: GRC rides again...
by owen＠dixon.delong.sj.ca.us 02 Jul '01

02 Jul '01

> On Mon, 02 Jul 2001 11:25:08 PDT, Mike Batchelor <mikebat(a)tmcs.net> said: > > > "Decades ago" implies more than one decade ago, which puts this purported > > statement by Novell sometime prior to 1981. That was a very prescient > > Umm.. does "one and a bit more" decades count? One decade ago was 1991, > and *two full* decades are required to get to 1981. > Does it really matter. The point is that over a decade ago, it was easily predictable that the folks in Redmond lacked clue, especially when it came to networking, cooperative networking, and security. Today, it is more clear than ever. Unfortunately, when it comes to computers, the people making the decisions seem to know little enough about them that they accept: Our car will allow you to do over 300 MPH As a good thing, ignoring the fact that the car lacks the ability to turn away from a brick wall or that the car requires that you buy all of your gasoline from the dealership. Owen

1 0

Re: Common causes of performance problems and outages
by Sean Donelan 02 Jul '01

02 Jul '01

On Mon, 02 July 2001, Maya wrote: > I want to find out the most common causes of > performance problems as well as outages in > networks today. Any information is welcome! In roughly the order 1. Network Engineers (What's this command do?) 2. Power failures (What's this switch do?) 3. Cable cuts (Backhoes, enough said) 4. Hardware failures (What's that smell?) 5. Congestion (More Bandwidth! Captain, I'm giving you all she's got!) 6. Attacks (malicious, you know who you are) 7. Software bugs (Your call is very important to us....)

1 0

Common causes of performance problems and outages
by Maya 02 Jul '01

02 Jul '01

Hello, I want to find out the most common causes of performance problems as well as outages in networks today. Any information is welcome! Maya Yajnik (myajnik(a)research.telcordia.com) Telcordia Technologies

2 1