[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Per-modules readers/writers ?

From: David R. Chase
Subject: Per-modules readers/writers ?
Date: Thu, 24 Oct 2002 16:49:08 -0400 (EDT)

Hello there,

Searched some of the archives but came up empty.  I don't think it's
supported, but I'm mainly asking to see if this will ever be implemented in
the future.

Basically, I'm wondering if there's any way to limit read/write access to a
repository on a modular level, that is, some users mapped in
$CVSROOT/CVSROOT/passwd will have read or write access to some modules,
while other users will have it for others.  I'm mainly trying to obtain
finer granularity access control via pserver (or other remote access)
authentication rather than via the filesystem's uid/gid and related
permissions.  With a fairly large repository, administration of large
groups of users for a large number of modules can become a nightmare if
done on the filesystem level without ACLs.  I'd rather have one system user
that a great number of developers are mapped to as virtual users, rather
than creating a new user or group for each project's members to access the
repository with.

If not, and I wanted to write a patch to add this feature, what would be
the best way to do it?  Have module-permissions defined in $CVSROOT/CVSROOT/
[readers,writers] or have permissions defineable in each module directory
such as $CVSROOT/module-name/config-dir/[readers,writers] ?  (personally, I
believe the second choice reduces overhead as the lookups could be done on
modular files rather than the global readers/writers files which could tend
to become very large).

Unless, of course, there's a better way to do what I want it to do, and not
on the filesystem level...  : )

Thanks in advance,
David R. Chase
College of Computer Science
Northeastern University, Boston

reply via email to

[Prev in Thread] Current Thread [Next in Thread]