RE: Use of suidmanager
It seems I misunderstood what suidmanager does.
But I still don't see the reason for non-setuid programs listed there
by default. Does that mean 'You can make this program suid, but we
prefer it to be not-suid.'?
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: Tuesday, June 24, 1997 4:51 PM
>To: Michael Meskes
>Cc: Die Adresse des Empfängers ist unbekannt.
>Subject: RE: Use of suidmanager
>On Tue, 24 Jun 1997, Michael Meskes wrote:
>>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?
>I am not sure that I understand this.
>/etc/suid.conf contains permission for suid candidates in order to make it
>easy to give those files suid status by simply editing the file.
>entries in suid.conf also will cause the preservation of those permissions
>--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
>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 .