This is the mail archive of the
mailing list for the Cygwin project.
Re: [ITP] libsuexec 1.0
- From: "D. Boland" <daniel at boland dot nl>
- To: Cygwin applications <cygwin-apps at cygwin dot com>
- Date: Thu, 21 Aug 2014 14:19:00 +0200
- Subject: Re: [ITP] libsuexec 1.0
- Authentication-results: sourceware.org; auth=none
- References: <53EF10B3 dot A1BC4FBE at boland dot nl> <53F100E0 dot CA2D4863 at boland dot nl> <871tsdhfmv dot fsf at Rainer dot invalid> <53F243E0 dot EA1E358E at boland dot nl> <87a96ybfxo dot fsf at Rainer dot invalid>
Achim Gratz wrote:
> D. Boland writes:
> >> I still think you should name it differently. Marco has already mixed
> >> it up with Apache suexecâ?¦
> > The idea kind of was to mix it up, so people will know what it does.
> Apache suexec is concerned with running new processes as a different
> user, so both the "su" and the "exec" part of the name make sense.
> Your library is concerned with inserting itself into certain calls to
> swap uid/gid so programs expecting a fixed mapping of some uid/gid to
> certain capabilities (roughly associated with the concept of a root
> user) work without the actual source getting patched on a system where
> those assumptions aren't true. Looks like different thing to me and
> giving it a different name surely wouldn't hurt.
Ok, got the point. But the "su" part must stay. Because it's the super-user who
needs to be simulated.
Suggestions are welcome...