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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070815192607.GE9410@csclub.uwaterloo.ca>
Date:	Wed, 15 Aug 2007 15:26:07 -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 10:59:12AM -0700, Marc Perkel wrote:
> When one thinks outside the box one has to think about
> evolving beyond what you are used to. When I moved
> beyond DOS I have to give up the idea of 8.3 file
> names. The idea here is to come up with a model that
> can emulate the existing system for backwards
> compatibility.

But moving beyond 8.3 didn't prevent you from still using 8.3 names if
you wanted too.  Longer file names are just an extension of shorter
ones.

> The concept behind my model is to create a new layer
> where you can do ANYTHING with file names and
> permissions and create models that emulate Linux, DOS,
> Windows, Mac, or anything else you can dream of. Then
> you can create a Linux/Windows/Mac template to emulate
> what you are used to.

I am not even sure your idea could represent everything that is
currently possible with Posix ACLs and the standard unix permisions,
never mind SELinux.  I am also almost entirely convinced that your idea
would be amazingly slow and inefficient and a serious pain to use.  And
of course nothing seems to ever suceed without backwards compatibility
to support legacy programs until new ones take over, unless it is in
fact an entirely new concept for a new field and isn't trying to replace
some existing working system.

--
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