Update of /cvsroot/cvs-nserver/cvs-nserver/www
In directory sc8-pr-cvs1:/tmp/cvs-serv14789/www
Modified Files:
Tag: NCLI-1-11-1
acl-cli.txt acl-rfc.txt
Added Files:
.cvsignore BRANCHES Makefile index.html logging-rfc.txt
ncli-architecture.txt
Log Message:
Merged NCLI-1-11-1 code w/ CVS 1.11.5
Index: acl-cli.txt
===================================================================
RCS file: /cvsroot/cvs-nserver/cvs-nserver/www/Attic/acl-cli.txt,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -d -r1.1.2.4 -r1.1.2.5
--- acl-cli.txt 14 Apr 2002 19:12:13 -0000 1.1.2.4
+++ acl-cli.txt 22 Apr 2003 18:56:59 -0000 1.1.2.5
@@ -140,7 +140,7 @@
Notes:
-Please not that "recursive" operations are not implemented, and that's
+Please note that "recursive" operations are not implemented, and that's
intentionally. Use default file operations instead. Remember that
directory permissions are checked from the top.
Index: acl-rfc.txt
===================================================================
RCS file: /cvsroot/cvs-nserver/cvs-nserver/www/Attic/acl-rfc.txt,v
retrieving revision 1.1.2.7
retrieving revision 1.1.2.8
diff -u -d -r1.1.2.7 -r1.1.2.8
--- acl-rfc.txt 31 Mar 2002 18:22:13 -0000 1.1.2.7
+++ acl-rfc.txt 22 Apr 2003 18:56:59 -0000 1.1.2.8
@@ -17,14 +17,6 @@
Primary Authorization Features
===============================
-The concept of "no ACL" is used a lot, and this could sometimes lead
-to (unexpected) opening of repository to extemely wide access. In
-short, when the ACL file is non-existent or becomes empty after
-revoking all privileges granted, the "default ACLs" come into play.
-Default ACLs simply allow everything. Maybe we need some flag file in
-the repository that means "default ACLs is deny everyone".
-
-
We need the following basic authorization features:
- the ACLs are assigned on per-file-on-branch, not on per-file basis.
|
