From owner-freebsd-security Fri Jan 29 15:58:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04356 for freebsd-security-outgoing; Fri, 29 Jan 1999 15:58:31 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04346 for ; Fri, 29 Jan 1999 15:58:29 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id SAA10873; Fri, 29 Jan 1999 18:49:06 -0500 (EST) Date: Fri, 29 Jan 1999 18:49:06 -0500 (EST) To: Igor Roshchin cc: security@FreeBSD.ORG Subject: Re: Sendmail- headers In-Reply-To: <199901292229.QAA22729@alecto.physics.uiuc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 29 Jan 1999, Igor Roshchin wrote: > but I am concerned if there was a break in this way, and whether I should > worry about detection of any traces of it. As I recall this was just used to mask the sender's identity, and did not lead to actual application overflow/root access-type exploits. I may be wrong though, so I would upgrade (it's since been fixed). -- Mike Hoskins System/Network Administrator SEI Data Network Services, Inc. http://www.seidata.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message