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]

Message-ID: <20031207144803.GB25971@folly>
From: markus at openbsd.org (Markus Friedl)
Subject: Partial Solution to SUID Problems

> 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.

it's not really necessary to have passwd setuid.  
you just can write a passwd server process and the passwd(8)
just talks to this server via unix domain sockets.  the server
can use getpeereid(2) or a similar machanism to figure
out the uid of the connecting user (dugsong has implemented
this).

similar things can be done for ping (just used fd passing
to get a raw socket).