[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-user
Subject:    Re: Gaining ownership of an inode in own directory using vim :w!
From:       Joel Rees <joel.rees () gmail ! com>
Date:       2013-07-29 23:17:46
Message-ID: CAAr43iNVV7+vrzDY7LKpEL5h1_ztpuk+wkoehvm9sByFmO8vgA () mail ! gmail ! com
[Download RAW message or body]

(The subject still isn't quite right, but it's closer.)

On Thu, May 23, 2013 at 7:48 AM, Beco <rcb@beco.cc> wrote:

>
> Dear users,
>
> I'm astonished by this (maybe I'm naive and I'm missing something).
>
> Yesterday as root I saved a file skel.bashrc in my /home/beco user, owned
> by root, group root.
>
> Today I edited it, logged as beco, and vi told me "warning, read only!". I
> edited anyway, just to test, and saved with :w!
>
> After that I checked the file and it has changed to owner beco, group beco.
>
> How is that possible?
>
> Thanks,
> Beco
>

You know, it occurs to me just now to wonder whether this misconception
about the difference between privileges on an object and privileges on the
holding container is part of the motivation behind all the churn on ACLs
and their ilk. (And, by extension, the unreasoning trust in the DMCA, as
opposed to trusting the US Constitution as it should have been.)

--
Joel Rees

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">(The subject still \
isn&#39;t quite right, but it&#39;s closer.)<br></div><div class="gmail_quote"><br>On \
Thu, May 23, 2013 at 7:48 AM, Beco <span dir="ltr">&lt;<a href="mailto:rcb@beco.cc" \
target="_blank">rcb@beco.cc</a>&gt;</span> wrote:<br> <blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr"><div><br></div><div>Dear users,</div><div><br></div><div>I&#39;m astonished \
by this (maybe I&#39;m naive and I&#39;m missing something).</div> \
<div><br></div><div>Yesterday as root I saved a file skel.bashrc in my /home/beco \
user, owned by root, group root.</div> <div><br></div><div>Today I edited it, logged \
as beco, and vi told me &quot;warning, read only!&quot;. I edited anyway, just to \
test, and saved with :w!</div><div><br></div><div>After that I checked the file and \
it has changed to owner beco, group beco.</div>

<div><br></div><div>How is that \
possible?</div><div><br></div><div>Thanks,</div><div>Beco</div><span \
class="HOEnZb"></span></div></blockquote></div><br></div><div class="gmail_extra">You \
know, it occurs to me just now to wonder whether this misconception about the \
difference between privileges on an object and privileges on the holding container is \
part of the motivation behind all the churn on ACLs and their ilk. (And, by \
extension, the unreasoning trust in the DMCA, as opposed to trusting the US \
Constitution as it should have been.)<br> </div><div \
class="gmail_extra"><br>--<br>Joel Rees </div></div>


-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAAr43iNVV7+vrzDY7LKpEL5h1_ztpuk+wkoehvm9sByFmO8vgA@mail.gmail.com


[prev in list] [next in list] [prev in thread] [next in thread]