full-disclosure - Partial Solution to SUID Problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: todd at hostopia.com (Todd Burroughs)
Subject: Partial Solution to SUID Problems

> please explain how a user should be able to change his password
> without a setuid passwd. write access to /etc/spwd.db and pwd.db for
> everybody...?

On a box that has user access, you would need more things suid.
I mostly administer web servers and a lot of other servers that people
have no need to really interact with.  They change passwords, etc.
through a web application and it has nothing to do with the actual
server.

On a server that you have shell access, you probably really need to add
'passwd' to the 'suid partitiion'.  You may need some other things,
on some of our servers, I have 'ping' as well.

As I said, this gives you some control and, regardless if you do this,
you should have the minimum number of s[ug]id programs to make your
system functional.  Start with 'su' and 'sendmail' for a server, for
a workstation, you'll probably need a couple to run X properly and
probably some for convenience.

Todd