lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 15 Aug 2007 17:04:00 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Marc Perkel <mperkel@...oo.com>
Cc:	Kyle Moffett <mrmacman_g4@....com>,
	Michael Tharp <gxti@...tiallystapled.com>,
	alan <alan@...eserver.org>,
	LKML Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Thinking outside the box on file systems

On Wed, Aug 15, 2007 at 01:44:50PM -0700, Marc Perkel wrote:
> Yes - that's a good example. Git is far more powerful
> and a different paradigm for CVS. Someone had to think
> outside the box and come up with a new way of looking
> at things. I'm trying to do something like that with
> this idea.
> 
> To me it make more sense to get rid of file
> permissions and look at people permissions. It reminds
> me of a story a friend of mine told about her 4 year
> old son.
> 
> The story was that they were driving down the road
> when they saw a wheel come off a truck. The son said,
> "look mommy, that wheel lost it's truck."
> 
> To me files are like the wheel. Rather than having the
> file know all it's owners it makes more sense for the
> owners to know it's files.

Except for the fact that on most systems each owner may have millions of
files, while very rarely does a file have more than a few dozen owners
or groups.  Having to wade through the permissions of millions of things
seems like a lot more work than checking a few dozen things.

Also the thing is that I care who can access files, while I do not
really care what particular set of files a user has access to.  It is
the data I am protecting, not the user.

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ