Todd Denniston wrote:
CLIP
The only reason I am using pserver is that it allows my users to have
CVAS controlled access to the respositories without giving them dierct
write access to them. If you can suggest another way of doing that, I'd
be glad to use it.
As Far As I Know, you are
Julian Opificius wrote:
SNIP
Thanks for this input!
The problem is that each of these articles achieve their intended
results by restricting commands to cvs. I don't want to do that: my
CVS users are my engineering department members with legitimate logins.
It's only access to the CVS
Todd Denniston wrote:
Big question: What do you think using :pserver: at this point, gain you and
your users over just :ext: over ssh?
Because they already have (and will continue to have) valid system shell
login, from here it only looks like more admin trouble to setup and maintain
Mark D. Baushke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius [EMAIL PROTECTED] writes:
Larry Jones wrote:
Julian Opificius writes:
I'm not quite sure what you mean by mapping users.
Using the third field of the CVSROOT/passwd file to have the server
run
as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius [EMAIL PROTECTED] writes:
The only problem now is that if a cvsadmin user introduces a directory
into the cvs repository using add, the directory is owned by him, not
by the global cvs user, and nobody else can check into/out of
Mark D. Baushke wrote:
The only problem now is that if a cvsadmin user introduces a directory
into the cvs repository using add, the directory is owned by him, not
by the global cvs user, and nobody else can check into/out of that
directory.
How do I automatically force new directories
Hi Julian.
Julian Opificius wrote:
Mark D. Baushke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius [EMAIL PROTECTED] writes:
The only problem now is that if a cvsadmin user introduces a directory
into the cvs repository using add, the directory is owned by him, not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius [EMAIL PROTECTED] writes:
Mark D. Baushke wrote:
The only problem now is that if a cvsadmin user introduces a directory
into the cvs repository using add, the directory is owned by him, not
by the global cvs user, and nobody
Larry Jones wrote:
Julian Opificius writes:
I just instigated admin controls by opening up and configuring the
UserAdminOptions setting.
My account is a member of Linux cvsadmin group, yet like
non-privileged users I cannot execute admin commands.
Then you're not really a member of the
Julian Opificius writes:
I just instigated admin controls by opening up and configuring the
UserAdminOptions setting.
My account is a member of Linux cvsadmin group, yet like
non-privileged users I cannot execute admin commands.
Then you're not really a member of the cvsadmin group. If
Julian Opificius writes:
That's the confusing thing; id tells me I'm a member of cvsadmin. Is
there any restriction about userid range? I'm 1000, cvsadmin group is 502.
In that case, my guess is that you're not using your account, you're
using the generic cvs account (you say all of your CVS
Larry Jones wrote:
Julian Opificius writes:
That's the confusing thing; id tells me I'm a member of cvsadmin. Is
there any restriction about userid range? I'm 1000, cvsadmin group is 502.
In that case, my guess is that you're not using your account, you're
using the generic cvs account (you
Julian Opificius writes:
I'm not quite sure what you mean by mapping users.
Using the third field of the CVSROOT/passwd file to have the server run
as some user other than the actual user.
I want each user to
have his own login to the system, and I want to control access to CVS
Larry Jones wrote:
Julian Opificius writes:
I'm not quite sure what you mean by mapping users.
Using the third field of the CVSROOT/passwd file to have the server run
as some user other than the actual user.
Yep, that's what I am/was doing.
I want each user to
have his own login to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius [EMAIL PROTECTED] writes:
Larry Jones wrote:
Julian Opificius writes:
I'm not quite sure what you mean by mapping users.
Using the third field of the CVSROOT/passwd file to have the server
run
as some user other than the
Julian Opificius wrote:
SNIP
I have one more issue that affects my choice that I should have
mentioned earlier. We are working in an FAA-regulated environment, and
my CVS respository must be secure, in that nobody can impair the
lifecycle data, and all accesses must be documented and
Julian Opificius writes:
I have one more issue that affects my choice that I should have
mentioned earlier. We are working in an FAA-regulated environment, and
my CVS respository must be secure, in that nobody can impair the
lifecycle data, and all accesses must be documented and
17 matches
Mail list logo
