All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15875] Add an option to disable file/directory access controls for USB stick-type storage devices
Date: Thu, 9 Dec 2010 16:50:58 GMT	[thread overview]
Message-ID: <201012091650.oB9GovFA023147@demeter1.kernel.org> (raw)
In-Reply-To: <bug-15875-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=15875


sergey <sergey-feo@yandex.ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergey-feo@yandex.ru




--- Comment #13 from sergey <sergey-feo@yandex.ru>  2010-12-09 16:50:51 ---
Excuse me for my bad English :-)

Now we have many variants that can be implemented.

1. Disable rights control at VFS level or at formatting time. 
a) at VFS level only (FS-independent)
b) at formatting time only (FS-dependent)
c) both at VFS level and at formatting time (FS level). Default option is
"rights on". It can be overwritted at FS level during formatting and then it
can be overwritted at VFS level during mounting.

My vote is 1c.

2. In case of VFS-level option - what UID, GID and mode will be set for created
files and directories?
a) as always. Independ of option "Disable rights control".
b) user root, group root, rwxrwxrwx.
c) something like umask option will be implemented.

In other words, we mount FS with disabling rights. Then we write something on
it. Then we remount FS with enabling rights. What permissions will we see?

My vote is 2a.

3. Lets imagine that we have ext3 filesistem mounted with "Disable right
control" option enabled. We run ls -l - what permissions will it show?
a) rwxrwxrwx
b) rwArwArwA, where A = true when at least one of "executable" bits on disk is
set to "true".

In other words, will our new option affect all rights or only read-write but
not exec?   

My vote is 3a (simple solution).

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-12-09 16:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29  9:29 [Bug 15875] New: Add options to disable POSIX acl for ext2/ext3/ext4 file systems bugzilla-daemon
2010-04-29  9:30 ` [Bug 15875] Add an option to disable file/directory permissions " bugzilla-daemon
2010-04-29  9:47 ` bugzilla-daemon
2010-04-29  9:54 ` bugzilla-daemon
2010-04-29  9:56 ` bugzilla-daemon
2010-04-29 10:16 ` bugzilla-daemon
2010-04-29 11:11 ` bugzilla-daemon
2010-05-06 12:36 ` bugzilla-daemon
2010-05-07  7:09 ` bugzilla-daemon
2010-05-31  7:50 ` [Bug 15875] Add an option to disable file/directory permissions for ACL'ed " bugzilla-daemon
2010-05-31  7:55 ` bugzilla-daemon
2010-07-04 14:25 ` bugzilla-daemon
2010-11-04 12:04 ` bugzilla-daemon
2010-11-04 15:48 ` bugzilla-daemon
2011-08-18 15:03   ` Chris Lee
2010-11-04 15:48 ` [Bug 15875] Add an option to disable file/directory access controls for USB stick-type storage devices bugzilla-daemon
2010-11-09 20:41 ` bugzilla-daemon
2010-12-09 16:50 ` bugzilla-daemon [this message]
2011-01-16 18:04 ` bugzilla-daemon

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=201012091650.oB9GovFA023147@demeter1.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.