From: Marc Perkel <mperkel@yahoo.com>
To: Michael Tharp <gxti@partiallystapled.com>
Cc: alan <alan@clueserver.org>, linux-kernel@vger.kernel.org
Subject: Re: Thinking outside the box on file systems
Date: Wed, 15 Aug 2007 10:51:02 -0700 (PDT) [thread overview]
Message-ID: <121831.55601.qm@web52502.mail.re2.yahoo.com> (raw)
In-Reply-To: <46C33835.90703@partiallystapled.com>
--- Michael Tharp <gxti@partiallystapled.com> wrote:
> Marc Perkel wrote:
> > That not a problem - it's a feature. In such a
> > situation the person would get a general file
> creation
> > error.
>
> Feature or not, it's still vulnerable to probing by
> malicious users. If
> there are create permissions on the directory, the
> invisibility is not
> perfect.
In a real world situation I would think that users
probing for invisible files is more secure that users
knowing the names of files that they have no access
to.
>
> > Although it isn't likely people would structure
> > files with invisible files in directories that the
> > user has create permissions [...]
>
> ... /tmp ...
You're still thinking inside the box. Let's take the
tmp directory for example. /tmp wpuld probably g away
in favor of persomal /tmp directories. As we all know,
/tmp is the source of a lot of vulnerabilities.
One might put a name translation mask on the /tmp name
in the file name translation system. For example:
/tmp -> my /tmp
Thus files written to /tmp would become /mperkel/tmp
and users wouldn't be able to see other users /tmp
files or have any name conflicts.
Let me explain about the concept of thinking outside
the box. If you run into a problem you figure out a
new solution. It's about finding ways to make things
work rather than finding ways to make things not work.
So - we are not only talking about a name permission
system but a file name translation system. Thus a
user's view of the file system might not be the same
for all users. In fact, let's say that mperkel is a
Windows user and is just attacking to Linus as a file
system. Because mperkel is in the windows group the
file system appears as h:\home\mperkel on a native
Linux level and mounts are drive letters. It would use
a Windows name translation mask program that would be
part of the permission/naming system.
Marc Perkel
Junk Email Filter dot com
http://www.junkemailfilter.com
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's
Comedy with an Edge to see what's on, when.
http://tv.yahoo.com/collections/222
next prev parent reply other threads:[~2007-08-15 17:51 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 22:45 Marc Perkel
2007-08-14 22:51 ` alan
2007-08-15 13:02 ` Michael Tharp
2007-08-15 13:30 ` Lennart Sorensen
2007-08-15 13:53 ` Kyle Moffett
2007-08-15 15:14 ` Michael Tharp
2007-08-15 16:36 ` Marc Perkel
2007-08-15 17:17 ` Kyle Moffett
2007-08-15 17:30 ` Marc Perkel
2007-08-15 18:22 ` Craig Ruff
2007-08-15 20:35 ` Marc Perkel
2007-08-16 11:27 ` Helge Hafting
2007-08-15 16:02 ` Marc Perkel
2007-08-15 16:57 ` Valdis.Kletnieks
2007-08-15 17:09 ` Marc Perkel
2007-08-15 17:22 ` Kyle Moffett
2007-08-15 17:34 ` Marc Perkel
2007-08-18 23:27 ` Alan
2007-08-18 23:26 ` Alan
2007-08-19 2:03 ` david
2007-08-19 2:57 ` Al Viro
2007-09-01 23:20 ` Oleg Verych
2007-08-15 19:20 ` Lennart Sorensen
2007-08-16 23:12 ` H. Peter Anvin
2007-08-15 16:58 ` Kyle Moffett
2007-08-15 17:19 ` Marc Perkel
2007-08-15 17:37 ` Kyle Moffett
2007-08-15 17:59 ` Marc Perkel
2007-08-15 19:26 ` Lennart Sorensen
2007-08-15 20:11 ` Kyle Moffett
2007-08-15 20:44 ` Marc Perkel
2007-08-15 21:04 ` Lennart Sorensen
2007-08-16 11:42 ` Helge Hafting
2007-08-16 12:09 ` linux-os (Dick Johnson)
2007-08-15 17:34 ` Phillip Susi
2007-08-15 17:53 ` Kyle Moffett
2007-08-15 18:05 ` Marc Perkel
2007-08-15 18:14 ` Kyle Moffett
2007-08-15 20:20 ` Marc Perkel
2007-08-15 20:43 ` Phillip Susi
2007-08-15 20:50 ` Marc Perkel
2007-08-15 21:20 ` Valdis.Kletnieks
2007-08-15 22:48 ` Marc Perkel
2007-08-16 3:42 ` Valdis.Kletnieks
2007-08-15 20:38 ` Phillip Susi
2007-08-15 21:17 ` Kyle Moffett
2007-08-15 22:14 ` Phillip Susi
2007-08-16 4:44 ` Kyle Moffett
2007-08-16 15:09 ` Phillip Susi
2007-08-16 15:29 ` Valdis.Kletnieks
2007-08-16 17:28 ` Phillip Susi
2007-08-16 17:31 ` Valdis.Kletnieks
2007-08-16 22:03 ` Phillip Susi
2007-08-16 23:17 ` Kyle Moffett
2007-08-17 4:24 ` Marc Perkel
2007-08-17 4:52 ` Valdis.Kletnieks
2007-08-17 15:19 ` Phillip Susi
2007-08-17 15:39 ` Valdis.Kletnieks
2007-08-17 19:01 ` Phillip Susi
2007-08-18 5:48 ` Kyle Moffett
2007-08-18 16:45 ` Marc Perkel
2007-08-18 18:19 ` Al Viro
2007-08-19 4:07 ` Marc Perkel
2007-08-20 7:05 ` Nix
2007-08-20 7:47 ` Brennan Ashton
2007-08-20 11:18 ` Marc Perkel
2007-08-20 13:32 ` linux-os (Dick Johnson)
2007-08-20 15:25 ` Lennart Sorensen
2007-08-20 15:26 ` Helge Hafting
2007-08-20 19:52 ` Nix
2007-08-20 16:21 ` [OT] " Randy Dunlap
2007-08-20 16:20 ` Xavier Bestel
2007-08-20 14:29 ` Phillip Susi
2007-08-20 15:13 ` Lennart Sorensen
2007-08-20 14:24 ` Phillip Susi
2007-08-15 22:40 ` Marc Perkel
2007-08-15 17:54 ` Marc Perkel
2007-08-15 17:02 ` Marc Perkel
2007-08-15 17:30 ` Michael Tharp
2007-08-15 17:51 ` Marc Perkel [this message]
2007-08-15 20:02 ` Yakov Lerner
2007-08-15 7:49 Tim Tassonis
2007-08-15 18:23 Brian Wheeler
2007-08-20 11:54 Tim Tassonis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=121831.55601.qm@web52502.mail.re2.yahoo.com \
--to=mperkel@yahoo.com \
--cc=alan@clueserver.org \
--cc=gxti@partiallystapled.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®