From owner-freebsd-security Sun Aug 22 13:56:42 1999 Delivered-To: freebsd-security@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5525F155C5 for ; Sun, 22 Aug 1999 13:56:37 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA03182 for freebsd-security@freebsd.org; Sun, 22 Aug 1999 22:56:53 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 1DF9B870A; Sun, 22 Aug 1999 22:36:19 +0200 (CEST) Date: Sun, 22 Aug 1999 22:36:19 +0200 From: Ollivier Robert To: freebsd-security@freebsd.org Subject: Re: getting passwored data via a perl cgi Message-ID: <19990822223619.B11240@keltia.freenix.fr> Mail-Followup-To: freebsd-security@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Colin Eric Johnson on Sun, Aug 22, 1999 at 09:57:31AM -0600 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5543 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Colin Eric Johnson: > Is there a way to allow other users access to complete password database? > I understand, basically, why this is restricted but I'm not sure how else > to solve this given FreeBSDs restrictions. Either you make it setuid root or you wipe up a daemon that runs as root and make your script discuss with the daemon. The daemon could cache entries for example (although pwd lookups should be fast thanks to the DB files). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message