This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [Libtirpc-devel] Fwd: Re: proposed patch to rpcbind to providefiner-grained security controls than offered by the -i option
On Sat, Dec 18, 2010 at 06:44:59PM -0500, Jeff Layton wrote:
> I can see arguments for either way. On the one hand, people porting to
> libtirpc are likely to be fixing code anyway -- fixing this ought to be
> doable at the same time. It's really not hard to call setgroups to fix
> up the groups list before you call this function.
When I originally reported the security issue with rpcbind that the -i option
opens up too many things, Chuck said it would be a simple recompile to build
with libtirpc and obviate that problem. But you seem to be saying that
significant porting is required. Is there a document somewhere describing the
issues that may arise in porting from glibc's rpc API to libtirpc?
It took me quite some time to chase down this getgroups issue. My
application SEGV'ed, and I ultimately tracked it down after a lot
of guesswork. The incompatibilies might not be so bad if they were
clearly documented somewhere -- perhaps /usr/share/doc/libtirpc/PORTING
is needed?
Regards,
Andy