Re: IMMUTABLE and APPEND-ONLY rationales

[David Ford]

This is a multi-part message in MIME format.
--------------E1DA3A19C4180615E2391EC2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris Evans wrote:

> We had securelevel in 2.0, and it's replaced by cap_bset in 2.2. The 2.2
> capability set wasn't sufficient to fully replicate securelevel. I've
> fixed that for 2.4 [1]
>
> So a mechanism to prevent even root from messing with
> append-only/immutable files _is_ in place [2]

So....what /proc file to we echo N to so as to effect securelevel?  :)

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."

--------------E1DA3A19C4180615E2391EC2
Content-Type: text/x-vcard; charset=us-ascii;
 name="david.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for David Ford
Content-Disposition: attachment;
 filename="david.vcf"

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
org:<img src="http://www.kalifornia.com/images/paradise.jpg">
adr:;;;;;;
version:2.1
email;internet:[e-mail]
title:Blue Labs Developer
x-mozilla-cpt:;28256
fn:David Ford
end:vcard

--------------E1DA3A19C4180615E2391EC2--