- Test - lists.nanog.org

Cisco IOS Exploit Cover Up
by James Baldwin 27 Jul '05

27 Jul '05

For those who like to keep abreast of security issues, there are interesting developments happening at BlackHat with regards to Cisco IOS and its vulnerability to arbitrary code executions. I apologize for the article itself being brief and lean on technical details, but allow me to say that it does represent a real problem (as in practical and confirmed): http://blogs.washingtonpost.com/securityfix/2005/07/mending_a_hole_.html

1 1

RE: Cisco IOS Exploit Cover Up
by Hannigan, Martin 27 Jul '05

27 Jul '05

> > > For those who like to keep abreast of security issues, there are > interesting developments happening at BlackHat with regards to Cisco > IOS and its vulnerability to arbitrary code executions. > > I apologize for the article itself being brief and lean on technical > details, but allow me to say that it does represent a real problem > (as in practical and confirmed): > > http://blogs.washingtonpost.com/securityfix/2005/07/mending_a_ > hole_.html > Yes, practical _and_ confirmed, but you'll never get $vendor to admit it, which is the problem to begin with. -M<

1 0

Not exactly off-topic, but sooooo not operational.
by Bill Woodcock 27 Jul '05

27 Jul '05

http://www.woodynet.net/Message%20No.%20419.mp3 -Bill

1 0

Extension For E911 "Not as Good As..." Rule
by Fergie (Paul Ferguson) 27 Jul '05

27 Jul '05

Following up from yesterday, Roy Mark writes this in internetnews.com: [snip] Voice over IP providers have another 30 days to inform customers of possible E911 emergency calling limitations -- or pull the plug on their service. After Aug. 30, VoIP providers will have to cut off subscribers who refuse to acknowledge the warning, according to the ruling by the Federal Communications Commission (FCC). The original deadline was Friday, July 29th. [snip] http://www.internetnews.com/infra/article.php/3523236 - ferg -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(a)netzero.net or fergdawg(a)sbcglobal.net ferg's tech blog: http://fergdawg.blogspot.com/

2 1

Overhaul of U.S. telecom law to be introduced
by Fergie (Paul Ferguson) 27 Jul '05

27 Jul '05

Via the EE Times: [snip] A Republican senator will unveil a rewrite of U.S. telecommunications laws on Wednesday (July 27). Sen. John Ensign, R-Nev., said he will introduce the Broadband Consumer Choice Act of 2005 during a Capitol Hill press conference. "The bill will improve consumers access to communication technology by rewriting outdated telecommunications laws," Ensign's office said in a statement. "One of the bills goals is to reduce government obstacles to technological innovation and expansion." The proposed legislation would replace the Telecommunications Act of 1996. [snip] http://www.eetimes.com/news/latest/showArticle.jhtml?articleID=166402650 - ferg -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(a)netzero.net or fergdawg(a)sbcglobal.net ferg's tech blog: http://fergdawg.blogspot.com/

3 3

freeserve/wanadoo contact
by Simon Waters 27 Jul '05

27 Jul '05

Anyone with clue at Wanadoo UK, or can put me in touch with someone, will do at this point. Specifically to do with their website hosting arrangements.

1 0

Re: NANOG List Server on several BlockLists
by Matthew Sullivan 27 Jul '05

27 Jul '05

Mikael Abrahamsson wrote: > On Wed, 27 Jul 2005, Matthew Sullivan wrote: > >> John Palmer wrote: >> >>> FYI: The IP address of the mail server that sends out NANOG list >>> messages >>> (198.108.1.26) is once again on most of the major RBLs. >> >> >> Was a mistake and was removed promptly as soon as we were notified. > > > What was the mistake? Would be informational to know how this happened > (again) and how it's not going to happen again in the future? I'm not going to give the gory details, but part of it was a mistake with a mouse click that I personally made. Ironically the main part of the reason it happened was because I was modifying the scripts to help prevent this sort of thing occuring in the future. Regards, Mat

1 0

NANOG List Server on several BlockLists
by John Palmer 27 Jul '05

27 Jul '05

FYI: The IP address of the mail server that sends out NANOG list messages (198.108.1.26) is once again on most of the major RBLs.

9 10

Internet phone providers given more time on 911
by Fergie (Paul Ferguson) 27 Jul '05

27 Jul '05

Wow, a whole month! A Reuters newswire article by Jeremy Pelofsky, via Yahoo! News, reports: [snip] Internet telephone service providers are getting a month longer to get their customers to acknowledge they know about the limitations of dialing 911 for help, U.S. communications regulators said on Tuesday. [snip] http://news.yahoo.com/news?tmpl=story&u=/nm/20050726/wr_nm/telecoms_voip_fc… - ferg -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(a)netzero.net or fergdawg(a)sbcglobal.net ferg's tech blog: http://fergdawg.blogspot.com/

2 1

6to4 routes disappeared from most of North America?
by Todd Vierling 27 Jul '05

27 Jul '05

Maybe I missed it, but was there some concerted effort to remove or block access to the 2002::/16 route on the v6 backbone in North America recently? Connectivity to/from 6to4-only hosts seems sketchy at best. Of the US hosts I've tried, only ISC has responded at all to a 6to4 packet -- and they're routing 2002::/16 through WIDE in Japan from what I can tell. >From about half the US IPv6 looking glasses I've tried, the route is missing entirely. By contrast, I can see it everywhere, typically from multiple upstreams, in JP (no surprise there), CH, DE, and FR that I've tried so far. I haven't been using 6to4 for almost 6 months now, but this seems like a really alarming step backwards as far as v6 adoptability goes in dynamic v4-pool environments. Yes, I'm aware of the security implications of 6to4 -- but if the RFC-suggested header address checks are properly performed at the ingress 6to4 gateway, the burden of security falls on the 6to4 user alone, which is (IMHO) an acceptable situation. -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

2 2