[3334] in Release_7.7_team
Jimmy Engelbrecht: Re: [OpenAFS] Re: Attacks against AFS lead to crashing machines
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Fri Jun 7 14:52:34 2002
Message-Id: <200206071852.OAA00931@brad-majors.mit.edu>
To: ops@MIT.EDU, release-team@MIT.EDU
Date: Fri, 07 Jun 2002 14:52:33 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
FYI. It looks like Irix is special in that it crashes even
running modern OpenAFS. There were also reports of AIX machines
running modern openafs clients, so this seems to have tickled more than
one bug across platforms.
------- Forwarded Message
Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by electric-barbarella.mit.edu (8.9.3) with ESMTP
id HAA22579; Fri, 7 Jun 2002 07:21:06 -0400 (EDT)
Received: from grand.central.org (GRAND.CENTRAL.ORG [128.2.194.109])
by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id HAA12548;
Fri, 7 Jun 2002 07:21:05 -0400 (EDT)
Received: from grand.central.org (localhost.localdomain [127.0.0.1])
by grand.central.org (Postfix) with ESMTP
id C4F109C15; Fri, 7 Jun 2002 07:21:02 -0400 (EDT)
Delivered-To: openafs-info@openafs.org
Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5])
by grand.central.org (Postfix) with ESMTP id CCD6C9C15
for <openafs-info@openafs.org>; Fri, 7 Jun 2002 07:20:42 -0400 (EDT)
Received: from gladiusit.e.kth.se (gladiusit.e.kth.se [130.237.48.34])
by elixir.e.kth.se (8.12.3/8.12.3) with ESMTP id g57BKe2I085601;
Fri, 7 Jun 2002 13:20:40 +0200 (CEST)
Received: (from jimmy@localhost)
by gladiusit.e.kth.se (8.11.6/8.9.3) id g57BKea26486;
Fri, 7 Jun 2002 13:20:40 +0200
X-Authentication-Warning: gladiusit.e.kth.se: jimmy set sender to jimmy@e.kth.se using -f
To: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] Re: Attacks against AFS lead to crashing machines
References: <20020606174601.GB2677@afs.mcc.ac.uk>
From: Jimmy Engelbrecht <jimmy@e.kth.se>
In-Reply-To: <20020606174601.GB2677@afs.mcc.ac.uk>
Message-ID: <aj8z5rqqrb.fsf@gladiusit.e.kth.se>
Lines: 16
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: openafs-info-admin@openafs.org
Errors-To: openafs-info-admin@openafs.org
X-BeenThere: openafs-info@openafs.org
X-Mailman-Version: 2.0.4
Precedence: bulk
List-Help: <mailto:openafs-info-request@openafs.org?subject=help>
List-Post: <mailto:openafs-info@openafs.org>
List-Subscribe: <https://lists.openafs.org/mailman/listinfo/openafs-info>,
<mailto:openafs-info-request@openafs.org?subject=subscribe>
List-Id: OpenAFS Info/Discussion <openafs-info.openafs.org>
List-Unsubscribe: <https://lists.openafs.org/mailman/listinfo/openafs-info>,
<mailto:openafs-info-request@openafs.org?subject=unsubscribe>
List-Archive: <https://lists.openafs.org/pipermail/openafs-info/>
Date: 07 Jun 2002 13:20:40 +0200
Dr A V Le Blanc <LeBlanc@mcc.ac.uk> writes:
> We had all three of our AFS fileservers crash; these are Silicon
> Graphics machines running IRIX 6.5 and using OpenAFS 1.2.3 (and
> now running OpenAFS 1.2.4). The IP address mentioned does not
> appear in any logs, but it may have escaped logging.
We just tested our code on Openafs 1.2.3 on IRIX, the machine crashed, we
are now analyzing the coredump.
However this one seems to be another bug in the code. Which means my
"afscrawler" triggers at least 2 different bugs.
We were not able to trigger the bug on Solaris 8 running openafs 1.2.2.
/Jimmy
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
------- End of Forwarded Message
