From owner-freebsd-questions@FreeBSD.ORG Thu Jul 17 20:15:27 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5842C37B401 for ; Thu, 17 Jul 2003 20:15:27 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8FC043F75 for ; Thu, 17 Jul 2003 20:15:25 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id CF58966E6A; Thu, 17 Jul 2003 20:15:24 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id AD74EC14; Wed, 16 Jul 2003 16:33:04 -0700 (PDT) Date: Wed, 16 Jul 2003 16:33:04 -0700 From: Kris Kennaway To: Josh Brooks Message-ID: <20030716233304.GA30013@rot13.obsecurity.org> References: <20030715233938.P36933-100000@mail.econolodgetulsa.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline In-Reply-To: <20030715233938.P36933-100000@mail.econolodgetulsa.com> User-Agent: Mutt/1.4.1i cc: freebsd-questions@freebsd.org Subject: Re: No /proc or procfs by default in 5.1-RELEASE ... why ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 03:15:27 -0000 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 15, 2003 at 11:42:49PM -0700, Josh Brooks wrote: >=20 > Hello, >=20 > As I am sure many have noticed, a default installation of 5.1-RELEASE will > leave you with no procfs mounted at /proc, and no entry in /etc/fstab for > a procfs. >=20 > Is this by design ? Yes. Historically speaking procfs is a huge security risk. > Is it better to not run /proc on 5.x ? If you run a multi-user system with untrusted users, yes. > What are the consequences of running without a procfs on 5.x ? You can't use truss(1) to monitor syscalls, but ktrace still works fine. Kris --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/FeCwWry0BWjoQKURAtcAAKDr+kKdyxkrI5Hoed/o9DR8eVsYZwCdEZUv pm6PFUFAVnKqcXA9yPFH3/A= =UASR -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6--