On Fri, 19 Jul 2013 08:20:27 -0500
John McKown <john.archie.mck...@gmail.com> wrote:

> In order to limit access to one or more directories (folders) or
> files, you must use the facilities with the host operating system.
> Because you said "folder" instead of "directory", I assume that you
> are running Windows. I don't _do_ Windows <grin/>. On a real OS, like
> UNIX or Linux, you can use Access Control Lists (ACLs) to enforce
> limits on a user's abilities. I would hope that Windows has something
> similar.

Oh, come on!  I admire your contribution to this list, but please
quit spreading FUD *in this particular case:* everyone long forgot
Windows 9x and FAT, and every sensible Windows flavor (I mean those
OSes based on the NT kernel and its modifications) require their system
partition to be on NTFS which has full support for ACLs by design, and
these ACLs do actually work.  Yes, ACLs are complicated, and yes,
stock Windows' and 3rd-party software tend to have an unfortunate
property of not paying much attention to security (services (think of
daemons) usually run under the "LOCAL SYSTEM" account (think of root),
and there's often little to no separation between the place containing
the program code/data and the stuff program writes itself (think
of /usr/bin + /usr/sbin vs /var/lib + /var/spool separation as per FHS)
but this is no excuse for blindly bashing Windows.

Also I'm quite sure you know that reasonably few people use POSIX
ACLs -- they are not even enabled in default mount options for most
filesystems (in Linux, I have little experience with BSDs and more
exotic stuff -- they might have other defaults of implementations of

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to