From owner-freebsd-security  Sat Jun 27 03:26:24 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA23496
          for freebsd-security-outgoing; Sat, 27 Jun 1998 03:26:24 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23488
          for <freebsd-security@FreeBSD.ORG>; Sat, 27 Jun 1998 03:26:21 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA28464;
	Sat, 27 Jun 1998 03:26:51 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: bow <bow@bow.net>
cc: Igor Roshchin <igor@physics.uiuc.edu>, freebsd-security@FreeBSD.ORG
Subject: Re: (FWD) QPOPPER REMOTE ROOT EXPLOIT 
In-reply-to: Your message of "Sat, 27 Jun 1998 02:21:02 PDT."
             <v03110701b1ba0652ee75@[204.210.38.36]> 
Date: Sat, 27 Jun 1998 03:26:51 -0700
Message-ID: <28461.898943211@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> This is a realllly quick fix.
> There is probably 100 ways to do it better, but this is better then turning
> qpopper off.

I've already committed a slightly more intelligent fix to this
problem.  Thanks!

- Jordan

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