Bug#709625: protected_hardlinks is too broad - make it per-filesystem instead?
On Sun, May 26, 2013 at 03:31:03AM +0100, Ben Hutchings wrote:
>On Fri, 2013-05-24 at 15:30 +0100, Steve McIntyre wrote:
>>
>> Alternatively, I'm pondering: if the main thrust of the hardlink
>> protection is to prevent attacks against system files, then it might
>> make more sense to change protected_hardlinks to be a per-filesystem
>> mount option. By all means protect the root filesystem etc., but for a
>> purely data-carrying filesystem it's a bit obstructive.
>>
>> What do you think?
>
>I can see that this could be a useful feature, but I don't think I can
>spare the time to work on it any time soon. If you have the time to
>implement this yourself, I would be happy to review the changes but you
>will need to submit them upstream.
OK, understood. I'll see if I can find some tuits...
--
Steve McIntyre, Cambridge, UK. steve@einval.com
Is there anybody out there?
Reply to: