From: David Bruzos <David.Bruzos@jaxport.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Optionally enforced time-based ACLs for BTRFS
Date: Thu, 26 Apr 2012 15:30:39 -0400 [thread overview]
Message-ID: <DE6EA944EF16AF4CA4C0D1856C83808006C7F05E96@ex7> (raw)
Hi BTRFS folks:
In my organization, many use cases exist for a time-based honoring field for FS ACLs. I've done some brief research regarding this topic, but I was unable to find any reference to such a thing in any file system.
I understand that a feature like time-based honoring for ACLs may arguably be something that should exist in higher layers (E.G. some document management system), but on the other hand, I see no real reason that an extra ACL field that would allow for time-based granting/removing of permissions to some user would be a problem.
* The logic would go something like this (ACE means Access control Entry):
If ACE.time = 0 or ACE.time > current_time; then
Honor ACE
Elif Ace.time < 0 and (current.time+ACE.time) > 0; then
Honor ACE
Else
not honor ACE
fi
for uses like company-wide file servers, etc, a little feature like that could go very far in long-term management of file system permissions. You could easily and non-hackeshly temporarily grant access to file system objects, without having to makemodifications to applications, system utilities,or system libraries. The behavior could be easily controled by mount options (could be off by default) and a small utility or function of the standard file system's utilities could allow for easy management of the value in the time fields (change, expire, etc).
Of course, acurit time would then be crutial to system security, but today acurit time is crytical on servers anyway in most situations. Besides, it would definitly be an optional feature, enabled at the user's choice.
If we add a second field, then both expire time and activation time could be set for a given access control entry at the same time. In that case, negative values for the fields could indicate things like restrict access to ---, r-x, etc, regardless of the ACE's actual content. Basically, it would be something like XFS's mask entry, but applying to the ACE itself not the entire list.
Any thoughts, suggestions, ideas?
Am I just plain crazy?
Thanks for the great work you're doing.
David Bruzos (Systems Administrator)
2831 Talleyrand Ave.
Jacksonville, FL 32206
Office: (904) 357-3069
________________________________________________________________________________________________
Please note that under Florida's public records law (F.S. 668.6076), most written communications
to or from the Jacksonville Port Authority are public records, available to the public and media
upon request. Your email communications may therefore be subject to public disclosure. If you have
received this email in error, please notify the sender by return email and delete immediately
without forwarding to others.
next reply other threads:[~2012-04-26 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:30 David Bruzos [this message]
2012-04-26 20:04 ` Optionally enforced time-based ACLs for BTRFS Chris Mason
2012-04-26 21:27 ` David Bruzos
2012-04-27 14:57 ` Chris Mason
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=DE6EA944EF16AF4CA4C0D1856C83808006C7F05E96@ex7 \
--to=david.bruzos@jaxport.com \
--cc=linux-btrfs@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.