From owner-freebsd-security  Tue May 22 13:32:53 2001
Delivered-To: freebsd-security@freebsd.org
Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40])
	by hub.freebsd.org (Postfix) with ESMTP id ECB0737B424
	for <freebsd-security@freebsd.org>; Tue, 22 May 2001 13:32:48 -0700 (PDT)
	(envelope-from glassfish@glassfish.net)
Received: from frogbox.glassfish.net ([64.230.59.63])
          by tomts7-srv.bellnexxia.net
          (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP
          id <20010522203248.NDVR16174.tomts7-srv.bellnexxia.net@frogbox.glassfish.net>
          for <freebsd-security@freebsd.org>;
          Tue, 22 May 2001 16:32:48 -0400
Received: (qmail 9346 invoked from network); 22 May 2001 20:35:34 -0000
Received: from unknown (HELO MAINWS) (192.0.0.20)
  by 192.0.0.4 with SMTP; 22 May 2001 20:35:34 -0000
From: "Michael Tang Helmeste" <glassfish@glassfish.net>
To: "Thomas T. Veldhouse" <veldy@veldy.net>,
	<freebsd-security@freebsd.org>
Subject: RE: Qmail + FreeBSD 4.3
Date: Tue, 22 May 2001 16:31:48 -0400
Message-ID: <GLECJJEOFFBMALIKCDHIAEHKCAAA.glassfish@glassfish.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <008701c0e2c1$4d3f6660$3028680a@tgt.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Importance: Normal
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-security.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-security>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-security>
X-Loop: FreeBSD.org

Well bad hardware is less likely than its trying to overwrite memory it
doesn't own. If he is being attacked, and it is a buffer overflow exploit,
than overwriting memory it doesn't own is more likely than it being
repeatidly hardware, especially after his system has been working fine all
this time.

-----Original Message-----
From: Thomas T. Veldhouse [mailto:veldy@veldy.net]
Sent: Tuesday, May 22, 2001 9:16 AM
To: Michael Tang Helmeste
Subject: Re: Qmail + FreeBSD 4.3


Signal 11 (and often10) very often signal bad hardware.  Memory and/or CPU
are usually the cause, followed by the main board.  Corruption occurs in
memory and a signal 11 results.

Tom Veldhouse
veldy@veldy.net

----- Original Message -----
From: "Michael Tang Helmeste" <glassfish@glassfish.net>
To: <freebsd-security@freebsd.org>
Sent: Monday, May 21, 2001 8:35 PM
Subject: RE: Qmail + FreeBSD 4.3


> actually it just means segmentation fault
>
> it happens when a program accesses some memory that it doesn't own
>
> -----Original Message-----
> From: owner-freebsd-security@FreeBSD.ORG
> [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Olivier Nicole
> Sent: Monday, May 21, 2001 9:17 PM
> To: subscribed@de-net.org
> Cc: freebsd-security@FreeBSD.ORG
> Subject: Re: Qmail + FreeBSD 4.3
>
>
> Hi Dan,
>
> Signa 11 often denotes some hardware problem I guess, something like
> overheating.
>
> Olivier
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message