Re: [Valgrind-users] FD leakage

[Robert W. <rj...@du...>]

> The new fd leakage reporting in valgrind 2.1.0 is a good
> addition. I have a couple of ideas that I would like to pass on.
> It would be nice if valgrind reported any fd > 2 when: system(),
> popen(), or exec() was called. This is almost always a security
> problem.=20

Just catching this on execve should be enough here, I think.  That
should catch all the other cases.

> Then there's a certain case that should get special attention. If
> the parent process leaks a listening descriptor, Bad Things can
> happen. A listening descriptor can be identified by 2 things, it
> is a socket and it has its address set to INADDR_ANY or
> IN6_IS_ADDR_UNSPECIFIED.

I can highlight this particularly loudly.

> Would this be hard to add? Does anyone else see the value of the
> above?

I can add this in but I'll probably make it so you have to enable it on
the command-line explicitly.  As John Reiser mentioned, there's probably
situations where this isn't a problem and I don't want it annoying
people in this case.

Regards,
 Robert.

--=20
Robert Walsh
Amalgamated Durables, Inc.  -  "We don't make the things you buy."
Email: rj...@du...