- Test - lists.nanog.org

RE: Delivery Status Notification (Failure)
by Michel Py 16 Sep '03

16 Sep '03

Mee too. -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Mike Damm Sent: Tuesday, September 16, 2003 3:17 PM To: nanog(a)merit.edu Subject: FW: Delivery Status Notification (Failure) Is anyone else seeing a sort of mail loop issue at ml.com? I'm getting odd bounces to list postings as well as a few duplicates of list mail. -Mike --- Michael Damm, MIS Department, Irwin Research & Development V: 509.457.5080 x298 F: 509.577.0301 E: miked(a)irwinresearch.com -----Original Message----- From: postmaster(a)win.ml.com [mailto:postmaster@win.ml.com] Sent: Tuesday, September 16, 2003 2:46 PM To: MikeD(a)irwinresearch.com Subject: Delivery Status Notification (Failure) This is an automatically generated Delivery Status Notification. Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop. nanog(a)merit.edu MikeD(a)irwinresearch.com ahu(a)ds9a.nl

2 1

FW: Delivery Status Notification (Failure)
by Mike Damm 16 Sep '03

16 Sep '03

Is anyone else seeing a sort of mail loop issue at ml.com? I'm getting odd bounces to list postings as well as a few duplicates of list mail. -Mike --- Michael Damm, MIS Department, Irwin Research & Development V: 509.457.5080 x298 F: 509.577.0301 E: miked(a)irwinresearch.com -----Original Message----- From: postmaster(a)win.ml.com [mailto:postmaster@win.ml.com] Sent: Tuesday, September 16, 2003 2:46 PM To: MikeD(a)irwinresearch.com Subject: Delivery Status Notification (Failure) This is an automatically generated Delivery Status Notification. Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop. nanog(a)merit.edu MikeD(a)irwinresearch.com ahu(a)ds9a.nl

2 1

RE: Not the best solution, but it takes VeriSign out of the loop
by Mike Damm 16 Sep '03

16 Sep '03

I have received a few replies off list suggesting the same. I already have access to the zones (well, not currently, moved to a new IP block and need to update my source address with them), and if I remember correctly, the agreement I had to sign restricts you from redistributing the data in any way shape and/or form. -Mike --- Michael Damm, MIS Department, Irwin Research & Development V: 509.457.5080 x298 F: 509.577.0301 E: miked(a)irwinresearch.com -----Original Message----- From: bert hubert [mailto:ahu@ds9a.nl] Sent: Tuesday, September 16, 2003 11:31 AM To: Mike Damm Cc: nanog(a)merit.edu Subject: Re: Not the best solution, but it takes VeriSign out of the loop > You can download the real zones if you want easily enough. Some years ago > all this took was sending a few faxes.

2 1

Eureka/GGN Listening?
by Drew Linsalata 16 Sep '03

16 Sep '03

If anyone from Eureka/GGN is listening, please drop me a note. -- Drew Linsalata The Gotham Bus Company, Inc. Colocation and Dedicated Access Solutions http://www.gothambus.com

1 0

Re: What *are* they smoking?
by Rich Braun 16 Sep '03

16 Sep '03

VeriSign stands to gain financially, take a look at this excerpt from an AP news blurb published yesterday: > Ben Turner, VeriSign's vice president for naming services, described the service > as a way to "improve overall usability of the Internet." > > People mistype ".com" and ".net" names some 20 million times daily, Turner said, > and internal studies show "the vast majority of users prefer a page like this > than what they are getting today." >... > Currently, Site Finder sends lost Web surfers to both regular search results and > pay-for-placement listings, which are marked as such. Turner said VeriSign was > partnering with two search companies he would not name. > > He would not disclose how much VeriSign would earn from those companies, with > which it has revenue-sharing arrangements. Anyone find out any details of the contracts which VeriSign has apparently signed to profit from this little venture? -rich

3 2

Vote early...
by Christopher X. Candreva 16 Sep '03

16 Sep '03

When you're done patching your resolver, and openssh, you might want to cast a vote for Stratton in their monthly CEO opinion poll. http://www.forbes.com/2003/05/01/cx_ceointernetpoll.html (Thanks to, uhm, someone who might not want to be named from OpenSRS for passing this along.) ========================================================== Chris Candreva -- chris(a)westnet.com -- (914) 967-7816 WestNet Internet Services of Westchester http://www.westnet.com/

1 0

RE: new openssh issue
by Ingevaldson, Dan (ISS Atlanta) 16 Sep '03

16 Sep '03

As promised, our advisory: http://xforce.iss.net/xforce/alerts/id/144 Regards, =============================== Daniel Ingevaldson Engineering Manager, X-Force R&D dsi(a)iss.net 404-236-3160 Internet Security Systems, Inc. The Power to Protect http://www.iss.net =============================== -----Original Message----- From: Ingevaldson, Dan (ISS Atlanta) Sent: Tuesday, September 16, 2003 4:01 PM To: Valdis.Kletnieks(a)vt.edu; Richard A Steenbergen Cc: William Allen Simpson; nanog(a)nanog.org Subject: RE: new openssh issue ISS X-Force discovered this vulnerability and our advisory will be released shortly. We were working to determine the full scope of the vulnerability before we notified the vendor. Unfortunately, someone else found the flaw and began to cause discuss it using specifics. That caused us to push forward our disclosure. Typically, when we do X-Force Advisories, we have developed an in-house, functional exploit (not proof of concept) in order to verify the exact nature and scope of the issue. We have not done so in this case. Right now it is undetermined if the issue is exploitable on *any* platform. It may turn out that it may be exploitable on every platform. This issue is serious enough that it should be addressed on all platforms as quickly as possible. I'll forward our Advisory to the list when it is public. Regards, =============================== Daniel Ingevaldson Engineering Manager, X-Force R&D dsi(a)iss.net 404-236-3160 Internet Security Systems, Inc. The Power to Protect http://www.iss.net =============================== -----Original Message----- From: Valdis.Kletnieks(a)vt.edu [mailto:Valdis.Kletnieks@vt.edu] Sent: Tuesday, September 16, 2003 3:50 PM To: Richard A Steenbergen Cc: William Allen Simpson; nanog(a)nanog.org Subject: Re: new openssh issue On Tue, 16 Sep 2003 15:33:03 EDT, Richard A Steenbergen said: > > patched, but does anybody know whether there's a problem with the > > criscos? (as in "how do I configure my router for that?" ;-) > > Or better yet, the OpenSSH running on Junipers? Nothing on Juniper's > site > about a vulnerability so far. A posting to full-disclosure quotes Theo as saying HP and Cisco are affected, and I don't see any reason that Juniper would *NOT* be, given the common code base of the OpenSSH implementations. I'm not going to say the routers are vulnerable, but I *would* say that ACLs blocking port 22 to the router might be a good idea.....

1 0

Root Server Operators (Re: What *are* they smoking?)
by John Neiberger 16 Sep '03

16 Sep '03

>>>> <joej(a)Rocknyou.com> 9/16/03 2:18:58 PM >>> > > >Just came across this: > >http://www.washingtonpost.com/wp-dyn/articles/A996-2003Sep12.html > Interesting and well-written. And ICANN had no comment. John --

1 0

Root Server Operators (Re: What *are* they smoking?)
by joej＠Rocknyou.com 16 Sep '03

16 Sep '03

Just came across this: http://www.washingtonpost.com/wp-dyn/articles/A996-2003Sep12.html

1 0

Re: Root Server Operators (Re: What *are* they smoking?)
by John Neiberger 16 Sep '03

16 Sep '03

>>>> "Robert A. Hayden" <rhayden(a)geek.net> 9/16/03 2:07:08 PM >>> > >On Tue, 16 Sep 2003, Damian Gerow wrote: >> How about, 'Internet Operators Across North America Struggle to Deal with >> Impact of Business Decision: Internet Functionality Worldwide >> Tampered With by Verisign'? There doesn't really appear to be a unified >> decision to do one thing, there's a lot of bandying ideas around, and >> 'wouldn't-it-be-cool-if's being thrown out. Given the technical nature of the issue perhaps someone from the list with excellent writing skills could author the 'press release'. Then, if someone else has some media or press contacts they could simply pass the release along to them. To be sure, that idea has a few problems but at least you have a chance to make sure the release contains factual information while still conveying the importance of the issue, two things that wouldn't be guaranteed if this were written up by a non-technical member of the press. Anybody know someone that works for AP or Reuters? Or maybe Wall Street Journal? :-) John --

1 0