On Mon, 08 Oct 2007 18:04:49 +0200, Pierre Habouzit wrote > The issue is that when the commands are run, the arguments can be > seen in clear text in `ps aux` output. > > So not only that script has the issue, the parts where you sed -e > "s/<password>/$PASSWORD/g" are vulnerable too.
Hi again Pierre, Yes, this is a really *big* issue. This is why one should prevent users to see processes running with another uid and/or gid (e.g. security.bsd.see_other_[u|g]ids sysctls on FreeBSD and hardened kernels on GNU/Linux) ! Unfortunalety, this is not always possible and there is no simple way to fix this flaw. Note this is not related to the ldapscripts : any admin running a 'standard' ldapadd command (or ldapmodify, ...) with the -w switch will encounter the same problem. I'll try to have a look at it. The idea of a file containing the passwd could be good... Any other idea is welcome :) Best regards, Ganaël LAPLANCHE [EMAIL PROTECTED] http://www.martymac.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
