RE: Use of suidmanager
But that means we have to add all permission since all are configurable.
Isn't it a better idea to save the standard setting only for those
programs that are setuid by default?
Dr. Michael Meskes, Projekt-Manager | topsystem Systemhaus GmbH
email@example.com | Europark A2, Adenauerstr. 20
firstname.lastname@example.org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
>From: Christoph Lameter [SMTP:email@example.com]
>Sent: Monday, June 23, 1997 5:45 PM
>Cc: Die Adresse des Empfängers ist unbekannt.
>Subject: Re: Use of suidmanager
>In article <199706231059.MAA07131@gauss.topsystem.de> you wrote:
>: Could anyone please tell me the advantages of suidmanager as it is right
>: now? I can see the usefullness of a tool like that, but I wonder if there
>: should be a daily test run to make sure no other file are suid. Or is this
>: dones elsewhere?
>Not all packages use suidmanager and thus the list in /etc/suid.conf is
>: Also why are there file in /etc/suid.conf that are not suid at all:
>: debmake /usr/bin/build root root 755
>: debmake /usr/bin/debpkg root root 755
>Suidmanager manages configurable permissions in general not only suid
>These binaries can be made suid. For example on my system:
>user /usr/bin/build root wheel 4754
>user /usr/bin/debpkg root wheel 4754
>I dont need sudo or other contraptions to build packages. More in
>/usr/doc/debmake. I can just type "build" and a packages goes through
>the complete build process.
>--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
>Please always CC me when replying to posts on mailing lists.
>TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
>Trouble? e-mail to firstname.lastname@example.org .
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .