Paul Sander wrote:
What are the modes of your directories right now? If you turn off
world read and execute access to an ancestor directory, users can't
penetrate the choke point without an ACL that accommodates
your access
policy.
OK, that sounds reasonable. On further discussions with
In our repository, we would like to be able to set up permissions so that
specific groups of people (in particular, co-op students who are only with
us for four months) can only check out from specific areas of the
repository. In general, full-time staff have access to most, if not all,
areas of
the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of Info-cvs digest...
Today's Topics:
1. 'checkoutinfo' trigger? (Jim.Hyslop)
--
Message: 1
Date: Wed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop [EMAIL PROTECTED] writes:
For us, an equivalent to the 'commitinfo' which
runs at checkout-time would be very useful. The
trigger would behave the same - an exit code of
0 allows the checkout to proceed, and a non-zero
exit code
Frank Knobloch wrote:
just try SINIS. (http://sinis.sourceforge.net/). This may help you.
Thanks for the tip - I'll have a look at it.
--
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal (
Mark D. Baushke wrote:
[snip use-case]
This differers from your case where only a portion
of the repository is restricted.
Interesting. Same idea, different subsections (as you say, an inverse of our
requirements).
I would think that the solution to your problem
would be that the commit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop [EMAIL PROTECTED] writes:
Mark D. Baushke wrote:
[snip use-case]
This differers from your case where only a
portion of the repository is restricted.
Interesting. Same idea, different subsections
(as you say, an inverse of our
Jim,
In our repository, we would like to be able to set up
permissions so that specific groups of people (in particular,
co-op students who are only with us for four months) can only
check out from specific areas of the repository. In general,
full-time staff have access to most, if
What are the modes of your directories right now? If you turn off
world read and execute access to an ancestor directory, users can't
penetrate the choke point without an ACL that accommodates your access
policy. This won't work with pserver, of course.
I'm glad to see another suggestion for
Hello,
I've added checkoutinfo to cvs-1.12.9, slightly based on a patch from
Andrey Aristarkhov that found in the mailinglist archive (but can't seem
to find again).
I use it to have more detailed control over who can checkout and commit
to specific repositories, directories and branches
I tend to agree. In my recent CVS project, I just went through
an exercise where I created an abstraction layer above all the
triggers currently available in CVS, to create such a consistent
interface. If the existing interface were more consistent, it
would have saved me some work.
Each of
ith bugs in CVS or this
manual" in the Cederqvist manual).
--Abstract End --
I would say, there is interest ;-0.
Larry, could you possibly gimme an overview of what is needed here,
in regards to the -t/-f flags? Why exactly did they switch it off?
Should cvswrappers be fixed or
PROTECTED] (bcc: Noel L Yap)
Subject: RE: Interest in checkoutinfo administration file?
On Thu, 4 May 2000, Leeuw, Guus (G.) wrote:
Larry Writes:
Valerianus Oey writes:
"cvs [server aborted]: -t/-f wrappers not supported by this version of
CVS
cvs [update aborted]: reading
agree with you that a badly designed script could be a problem.
This would be the responsibility of anyone that adds a script to "checkoutinfo"
to make sure it's secure and robust.
But, it does seem somewhat unlikely that a script could cause security problems
since the script
-Original Message-
From: Erik Kluzek [mailto:[EMAIL PROTECTED]]
Sent: 04 May 2000 06:25
To: Arthur Barrett
Cc: '[EMAIL PROTECTED]'
Subject: RE: Interest in checkoutinfo administration file?
On Thu, 4 May 2000, Arthur Barrett wrote:
I thought this was the point of cvswrappers
ecify what program to run to prevent
checkout.
One drawback here is that the modules file can be bypassed by full
path specifications, etc. The checkoutinfo trigger could not be
bypassed.
donald On Wed, May 03, 2000 at 02:22:46PM -0600, Erik Kluzek
wrote:
Is there any inter
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Noel L Yap)
Subject: Re: Interest in checkoutinfo administration file?
I'd be interested in this for the reasons you mention.
Noel
[EMAIL PROTECTED] on 05/03/2000 04:22:46 PM
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Interest
Erik Kluzek wrote:
Is there any interest in CVS having a "checkoutinfo" administration file?
Yes, yes, yes, yes, yes. I've read the other messages in this thread
and am not convinced that the modules file -o option will do what I want
in all cases. I've found several cases wher
Is there any interest in CVS having a "checkoutinfo" administration file?
This would be similar to "commitinfo" as it would run a script before
files are checked out. This way checkout could limit the versions checked out
or restrict access to branches etcetera. There are va
I thought this was the point of cvswrappers, which is currently disabled,
which is another point entirely...
grin
Is there any interest in CVS having a "checkoutinfo" administration file?
This would be similar to "commitinfo" as it would run a script before
files are c
:22:46PM -0600, Erik Kluzek wrote:
Is there any interest in CVS having a "checkoutinfo" administration file?
This would be similar to "commitinfo" as it would run a script before
files are checked out. This way checkout could limit the versions checked out
or restrict access
I'd be interested in this for the reasons you mention.
Noel
[EMAIL PROTECTED] on 05/03/2000 04:22:46 PM
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Interest in checkoutinfo administration file?
Is there any interest in CVS having a "checkoutinfo" administr
On Wed, 3 May 2000, Donald Sharp wrote:
What you are looking for is the modules file. Split your project
up into multiple modules. Each module being something you want
to restrict access to. Within the CVSROOT/modules file use
the -o program to specify what program to run to prevent
23 matches
Mail list logo
