From owner-freebsd-security Fri Mar 2 12: 0:25 2001 Delivered-To: freebsd-security@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id D675437B71B for ; Fri, 2 Mar 2001 12:00:22 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA06845; Fri, 2 Mar 2001 12:00:17 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200103022000.MAA06845@gndrsh.dnsmgr.net> Subject: Re: /etc/pwd.db In-Reply-To: from Matt Heckaman at "Mar 2, 2001 03:17:34 am" To: matt@LUCIDA.CA (Matt Heckaman) Date: Fri, 2 Mar 2001 12:00:16 -0800 (PST) Cc: mudman@R181204.resnet.ucsb.edu (mudman), freebsd-security@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Fri, 2 Mar 2001, mudman wrote: > ... > : So.... what do you guys think? > > Better yet: pwd.db doesn't even contain any passwords! It's the functional > equiv. of /etc/passwd. spwd.db contains the real passwords and is mode > 0600 root:wheel. :) > > No worries, other than the annoying DoS attacks. Actually one minor worry, the possible reason they went after /etc/pwd.db is that they needed a list of user names to attempt other means of entry to the system. Remeber access control is via 2 tokens, username and password, if you gain a list of usernames your task at hacking can be much easier. A good reason for going after /etc/pwd.db is that it is a world readable file, and thus sometimes easier to get a hold of. Find a clueless Luser in that list and you got a big foot in the door... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message