Basil V. Dolmatov wrote:
> ----- Forwarded message from Joe Shaw -----
> >From owner-bugtraq@NETSPACE.ORG Fri Jun 27 19:44:37 1997
> X-UIDL: eacfebd3fdcb42f73c46694505523c1b
> Return-Path: <owner-bugtraq@NETSPACE.ORG>
> Received: from brimstone.netspace.org (brimstone.netspace.org [184.108.40.206])
> by ns.east.ru (8.8.5/8.8.5/BD2) with ESMTP id TAA23501
> for <bugtraq@NS.EAST.RU>; Fri, 27 Jun 1997 19:44:34 +0400 (MSD)
> Received: from firstname.lastname@example.org (port 37382 [220.127.116.11]) by brimstone.netspace.org with ESMTP id <35415-9809>; Fri, 27 Jun 1997 11:38:37 -0400
> Received: from NETSPACE.ORG by NETSPACE.ORG (LISTSERV-TCP/IP release 1.8c) with
> spool id 4268343 for BUGTRAQ@NETSPACE.ORG; Fri, 27 Jun 1997 11:24:59
> Received: from brimstone.netspace.org (brimstone [18.104.22.168]) by
> netspace.org (8.8.5/8.8.2) with ESMTP id LAA02126 for
> <BUGTRAQ@NETSPACE.ORG>; Fri, 27 Jun 1997 11:14:09 -0400
> Received: from email@example.com (port 37382 [22.214.171.124]) by
> brimstone.netspace.org with ESMTP id <32915-9811>; Fri, 27 Jun 1997
> 11:14:14 -0400
> Approved-By: aleph1@UNDERGROUND.ORG
> Received: from insync.net (firstname.lastname@example.org [126.96.36.199]) by
> netspace.org (8.8.5/8.8.2) with ESMTP id RAA12655 for
> <email@example.com>; Thu, 26 Jun 1997 17:47:49 -0400
> Received: from localhost (jshaw@localhost) by insync.net (8.8.6/8.7.1) with
> SMTP id QAA05949 for <firstname.lastname@example.org>; Thu, 26 Jun 1997
> 16:47:50 -0500 (CDT)
> Message-ID: <Pine.GSO.3.96.970626161110.14535Eemail@example.com>
> Date: Thu, 26 Jun 1997 16:47:49 -0500
> Reply-To: Joe Shaw <jshaw@INSYNC.NET>
> Sender: Bugtraq List <BUGTRAQ@NETSPACE.ORG>
> From: Joe Shaw <jshaw@INSYNC.NET>
> Subject: Ascend DoS attack
> To: BUGTRAQ@NETSPACE.ORG
> Recently, we noticed a problem in Ascends microcode for the Ascend MAX
> 4000 that allowed any user to request any IP address they wanted. This
> problem surfaced in the 4.x versions of code, works on 5.0Ap8, and
> probably works on most of the versions of Ascend software.
> It was fixed originally some time ago (or at least thats what I was led to
> believe by Ascend), but the problem resurfaced recently. It will work,
> even if you have such things as Assign Adrs and Pool only set to yes.
Not valid since 5.0p10, also its very easy to catch the bad-ass(that tryin' to bug your lovelly max) due CLID at punish him for good.
ARKANOID: it CAN be DoS when you running OSPF process. Appearing of 2nd host with ip same to max make its dope somewhere thus hog all CPU.
Basil: I always knew it! You are in love with ASND ! Yeah ? (everybody say YEAH!)
broadcast: its not deadly(est?) ascend firmware current bugs. What you want at all? Its only 1.5 year old (CHEERS!). After year of endless sex with this masterpiece (max4k) i (still?!) saying that its not really bad hardware for its special purposes
P.S. Really sorry for english ( both of'em.. good and bad one) but... vt..
Thanks for collaboration, |#make universe
Lyamin Alex (sober?) |make: don't know how to make universe. Stop
fax-no: +7 095 9562205 |#man man
"inet-admins" Internet access mailing list. Maintained by East Connection ISP.
Mail "unsubscribe inet-admins" to Majordomo@east.ru if you want to quit.
List archive is accessible at http://www.east.ru/inet-admins/