On Thu, Aug 13, 2015 at 07:31:34PM +0200, Eduard Bloch wrote: > I have a similar problem - ping lost suid permission for unknown reason. > Reinstalling the package does not help (see below). Is this in the scope > of this bug report or do you wish a new one? > > $ apt-get --reinstall install iputils-ping > iputils-ping (3:20121221-5+b2) wird eingerichtet ... > Failed to set capabilities on file `/bin/ping' (Invalid argument) > The value of the capability argument is not permitted for a file. Or the file > is not a regular (non-symlink) file > Setcap failed on /bin/ping, falling back to setuid
I don't think that this is the same bug. The issue that precipitated this bug was that the postinst script simply never tried to set capabilities on the binaries at all during a reconfigure. Your issue sounds like something else. The output that you provided suggests that the iputils-ping postinst script did try to set the capabilities as expected, but that setcap failed for some reason. Please check to see if you can reproduce this by calling setcap manually, e.g. $ sudo setcap cap_net_raw+ep /bin/ping cap_net_raw+ep /bin/ping6 If this fails, then the problem isn't specifically with iputils but is some other issue with capabilities on your system. If it works, then the problem would seem to be with iputils somewhere and a new bug report would be appropriate and we can try to debug the issue in that context. Thanks noah
signature.asc
Description: Digital signature
