On Sat, Feb 16, 2013 at 05:53:05PM -0500, Laine Stump wrote:
On 02/16/2013 12:20 AM, Doug Goldstein wrote:
On Tue, Feb 12, 2013 at 2:15 PM, Laine Stump la...@laine.org wrote:
Normally when a process' uid is changed to non-0, all the capabilities
bits are cleared, even those explicitly set
On 02/18/2013 10:09 AM, Guido Günther wrote:
On Sat, Feb 16, 2013 at 05:53:05PM -0500, Laine Stump wrote:
On 02/16/2013 12:20 AM, Doug Goldstein wrote:
The following error bisect's down to this commit when running out of
my local checkout for testing.
2013-02-16 05:16:55.102+: 29992:
On Sat, Feb 16, 2013 at 4:53 PM, Laine Stump la...@laine.org wrote:
On 02/16/2013 12:20 AM, Doug Goldstein wrote:
On Tue, Feb 12, 2013 at 2:15 PM, Laine Stump la...@laine.org wrote:
Normally when a process' uid is changed to non-0, all the capabilities
bits are cleared, even those explicitly
On 02/16/2013 12:20 AM, Doug Goldstein wrote:
On Tue, Feb 12, 2013 at 2:15 PM, Laine Stump la...@laine.org wrote:
Normally when a process' uid is changed to non-0, all the capabilities
bits are cleared, even those explicitly set with calls to
capng_update()/capng_apply() made immediately
On Tue, Feb 12, 2013 at 2:15 PM, Laine Stump la...@laine.org wrote:
Normally when a process' uid is changed to non-0, all the capabilities
bits are cleared, even those explicitly set with calls to
capng_update()/capng_apply() made immediately before setuid. And
*after* the process' uid has
Normally when a process' uid is changed to non-0, all the capabilities
bits are cleared, even those explicitly set with calls to
capng_update()/capng_apply() made immediately before setuid. And
*after* the process' uid has been changed, it no longer has the
necessary privileges to add capabilities
On 02/12/2013 01:15 PM, Laine Stump wrote:
Normally when a process' uid is changed to non-0, all the capabilities
bits are cleared, even those explicitly set with calls to
capng_update()/capng_apply() made immediately before setuid. And
*after* the process' uid has been changed, it no longer
