Re: Un*x Security Experts

> [Apologies for the non-cross cross-post. I figured it was better than > missing any experts on php-dev who has decamped from php@, and at least any > over-zealous followups from php@ won't hit here.] > > It would seem that configuring a web-server and password changing is a hot > topic on the php@lists.host.net list. > > Alas, there is a dearth of clear, hard info on how to do this *AS* *SECURE* > *AS*, say, a user logging in via SSH, and typing passwd to change their > password. (Which is pretty secure, AFAIK.) > > Is this because it can't be done?... Or because you're all too busy?... > > If you could 'splain in technical terms to me offline, I'm willing to try > to translate it into "newbie" and add it to the FAQ. There are a number of security issues here. 1. Password going over the Net in cleartext 2. Password being passed from PHP to something that can actually change it 3. The something that can change the password needing root access to do so The only way to solve 1 is to use SSL. If we are talking about changing a system user's password, then 2 and 3 cannot be solved nicely and shouldn't be done anyway. At least not on any sort of shared server. If we are talking about changing a password for a .htaccess style auth system, then PHP should be used to edit whatever database is storing the passwords directly. Preferably by running a separate httpd as a different user id dedicated to administrative tasks like this. That way other people on the server that might have the ability to write PHP scripts will not be able to write something to mess with the password database. Alternatively safe-mode can be used server-wide but turned off for the password-changing script. -Rasmus