From owner-freebsd-security  Fri Sep 25 04:47:26 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA19937
          for freebsd-security-outgoing; Fri, 25 Sep 1998 04:47:26 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from maciek.gv.edu.pl ([195.117.86.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19291
          for <freebsd-security@freebsd.org>; Fri, 25 Sep 1998 04:43:20 -0700 (PDT)
          (envelope-from andrzej@maciek.gv.edu.pl)
Received: from localhost (andrzej@localhost)
	by maciek.gv.edu.pl (8.8.8/8.8.8) with SMTP id NAA01368
	for <freebsd-security@freebsd.org>; Thu, 24 Sep 1998 13:42:11 GMT
	(envelope-from andrzej@maciek.gv.edu.pl)
Date: Thu, 24 Sep 1998 13:42:10 +0000 (GMT)
From: Andrzej Szydlo <andrzej@maciek.gv.edu.pl>
To: freebsd-security@FreeBSD.ORG
Subject: Checking for uids 0 in /etc/security
Message-ID: <Pine.BSF.3.96.980924133020.1141A-100000@maciek.gv.edu.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

I've just noticed that /etc/security checks for strings "0" in the uid
field of the master.passwd file. 

awk 'BEGIN {FS=":"} $3=="0" {print $1, $3}' /etc/master.passwd
                    ^^^^^^ 
In this way it doesn't notice entries like this:

myroot:xxxx:000:000:....

while such an entry still gives uid 0.
Changing this line to:

awk 'BEGIN {FS=":"} $3==0 {print $1, $3}' /etc/master.passwd
                    ^^^^^
solves the problem.


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