From owner-freebsd-security Tue Jul 21 09:02:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16126 for freebsd-security-outgoing; Tue, 21 Jul 1998 09:02:03 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16090 for ; Tue, 21 Jul 1998 09:01:55 -0700 (PDT) (envelope-from jer@jorsm.com) Received: from localhost (jer@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id LAA08309; Tue, 21 Jul 1998 11:01:16 -0500 (CDT) Date: Tue, 21 Jul 1998 11:01:16 -0500 (CDT) From: Jeremy Shaffner To: Brett Glass cc: "Christopher G. Petrilli" , "Gentry A. Bieker" , security@FreeBSD.ORG Subject: Re: Why is there no info on the QPOPPER hack? In-Reply-To: <199807201845.MAA21839@lariat.lariat.org> 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 Mon, 20 Jul 1998, Brett Glass wrote: > Reliance on mailing lists such as Bugtraq does not do any more or less > to "replace the administrator's brain." Fact is, when a trusted authority > says that there's a hole to be closed, I want action. I'm perfectly content > to review what happened after the fact. > > --Brett Glass > Have you not gotten the message by now? The Qpopper problem is old news, and Jordan released patches to the popper port the same day. Pretty fast action I'd say, and I dunno, something tells me he's trustworthy, but I can't quite put my finger on it. Like everyone said, it was impossible to NOT know about it. Where were you? -===================================================================- Jeremy Shaffner JORSM Internet Senior Technical Support Northwest Indiana's Premium jer@jorsm.com Internet Service Provider support@jorsm.com http://www.jorsm.com -===================================================================- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message