| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/832271
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
| |
Not meant to be stable yet (accidentally pushed as).
Bug: https://bugs.gentoo.org/832092
Signed-off-by: Sam James <sam@gentoo.org>
|
|
su(1) is almost useless without suid and on balance, it's more likely
that people will have USE="-suid" in make.conf (globally) rather than
desperately wanting to strip su(1) of its suid bits.
This avoids such users having a "broken" (or dysfunctional) su(1).
Users wishing to truly have a no-suid su(1) can e.g. use Portage's
'suidctl' feature or strip it out via e.g. a bashrc hook.
Note that shadow's su(1) (the default implementation until recently)
always forced suid su anyway.
Closes: https://bugs.gentoo.org/832092
Signed-off-by: Sam James <sam@gentoo.org>
|