From owner-freebsd-current Tue Apr 18 5:43: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 58E8737B83F for ; Tue, 18 Apr 2000 05:42:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id OAA15890; Tue, 18 Apr 2000 14:42:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Julian Elischer , Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. In-reply-to: Your message of "Tue, 18 Apr 2000 05:35:37 PDT." <20000418123537.A24141CD7@overcee.netplex.com.au> Date: Tue, 18 Apr 2000 14:42:19 +0200 Message-ID: <15888.956061739@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000418123537.A24141CD7@overcee.netplex.com.au>, Peter Wemm writes : >Julian Elischer wrote: >> I presume this means that it should remain part of the standard system >> but that the source should be moved to /sys/i386/linux? >> >> as long as it remains part of the system I don't care where it lives.. >> It's too massively important to totally drop. Having it as a port was >> a losing proposition. > >The biggest problem is that it re-opens a security hole that was explicitly >patched in procfs. > >Also, the way I see it, the linux procfs should probably only be visible to >linux sysvec processes... It would be a damn shame to let >/compat/linux/procfs "sneak in" to the expected system requirements for bsd >programs so that developers can use the easy way out rather than doing >something properly. Fully agreement here, and that was also what the core decision said: only visible to processed run under the linuxolator. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message