Re: [reSIProcate] [repro-devel] setuid
Sounds reasonable to me. There probably is a windows api for doing
this, but that code can be filled in later.
Scott
> -----Original Message-----
> From: repro-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:repro-devel-
> bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Ryan Kereliuk
> Sent: Wednesday, May 02, 2007 8:56 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> Cc: repro-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [repro-devel] setuid
>
> One feature I'd like to add to repro is the ability to run as some
> specified user (e.g. repro --user username --group groupname) plus
> the ability to chroot(2) into a jail (e.g. repro --chroot dir).
> I'm doing this already with a repro wrapper but it would be nice to
> build right in. I think this is a Really good idea as we run beta
code
> on internet-attached hosts.
>
> My question, and the reason I sent this to resiprocate-devel, is what
> this
> means in a multiplatform scenario. My guess is that none of this maps
> to
> WIN32 whatsoever and that the remaining platforms will fall in line
> with
> the right includes and typedefs. Should I encapsulate the
> setuid/setgid
> stuff in rutil as resip::ProcessUser with lots of #ifndef WIN32?
>
> Followups to resiprocate-devel please!
>
> Thanks,
> -Ryan
> _______________________________________________
> repro-devel mailing list
> repro-devel@xxxxxxxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/repro-devel