Date: Mon, 24 Sep 2001 11:53:21 -0700 From: Sean Chittenden <sean@chittenden.org> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /dev/null permission change from 4.3 -> 4.4... Message-ID: <20010924115320.B33285@rand.tgd.net> In-Reply-To: <20010923183733.A73977@xor.obsecurity.org>; from "kris@obsecurity.org" on Sun, Sep 23, 2001 at = 06:37:33PM References: <20010923175213.B18824@rand.tgd.net> <20010923183733.A73977@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--bCsyhTFzCvuiizWE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > Howdy. This question was originally framed as a "why doesn't > > uptime work for users in 4.4, when it used to in 4.3," but after looking > > into things further, it's now a "why is /dev/null set to mod 0600?" On > > a 4.3 system that I have, the perms on dev/null are 666. >=20 > Something must have gone wrong.. I couldn't agree more. :) > it's still supposed to be 666, and is on my machines. I've gotten a few other reports from other people that have said that=20 /dev/random and /dev/urandom were also set to (6|4)00, so I don't think=20 it's an isolated event... on the other hand, it doesn't appear to be a=20 problem currently and is believed to have been just a one time=20 "feature". -sc --=20 Sean Chittenden --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden <sean@chittenden.org> iEYEARECAAYFAjuvgSAACgkQn09c7x7d+q2WgACgsHq++l1YX5TO9casnFCnPVJQ prAAnjE8+bxqX+5mB5yupphpzQZu8WaN =ikUj -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010924115320.B33285>