Re: Problem with CVS and group ownership.
On Wed, 2004-06-23 at 15:21, Vincent Hallberg wrote:
> The default umask on a fresh Debian install is:
> UMASK 022
>
> I've been thinking of adding users to the system this way to solve the
> problem:
> adduser -no-create-home --ingroup src | username
>
> I am running the pserver which starts up automatically but am not
> familier with how to add user's to the CVS that are not already normal
> user's on the system. Tortoisecvs's default connect method is
> pserver.
>
> Does this make any sense or should I be working this monster an
> entirely different way?
Hi Vincent,
Just a note; the convention in most email lists is to add your comments
mixed with or *below* the comments that are being responded to. This is
called "bottom posting", rather than adding comments at the top of the
email ("top posting"). The "bottom posting" style means an email makes
sense when read top-to-bottom...important in any situation, I think, but
critical when people may be picking up a "conversation" part-way
through.
And please reply to the list rather than direct. The email archives are
a very useful resource for other people to search, but that doesn't work
if all emails other than the first exchange are off-list. And if I screw
up and give bad advice, there won't be anyone watching to correct me :-)
When using "pserver", CVS keeps its list of valid users & passwords in
the file CVSROOT/passwd within the CVS repository. To add a CVS "user",
you just edit this file. There is no connection between "cvs user ids"
and users on the local system, nor is there any connection between a
user's CVS password (if any) and their OS login password.
For a cvs repository that is "internal" to a company, I usually just set
everyone's CVS password to "password" or similar; the aim of CVS user
accounts in this case is simply to provide distinct login accounts so
that changes are marked against users, not to apply security. But you
can have "real" passwords if you want. Just don't make them the same as
the OS login passwords, because when using pserver, CVS stores passwords
in a .cvspass file in each user's home dir, in plain text.
If you *do* care about strong authentication of your users, you should
probably not go the "pserver" route. But in that case I can't offer any
advice other than to allow plenty of time to get your access permissions
right! Or use SubVersion (subversion.tigris.org), which is far better
than CVS (though somewhat more resource-hungry).
Regards,
Simon
> -----Original Message-----
> From: Simon Kitching <simon@ecnetwork.co.nz>
> To: Vincent Hallberg <vincent.hallberg@secret-agent.net>
> Cc: debian-user@lists.debian.org
> Date: Wed, 23 Jun 2004 13:40:06 +1200
> Subject: Re: Problem with CVS and group ownership.
>
> > On Wed, 2004-06-23 at 12:53, Vincent Hallberg wrote:
> > > Package: cvs
> > >
> > > Version: 1:1.12.9-1
> > >
> > >
> > >
> > > In order to share files between normal users on CVS Ive added them
> > to
> > > the src group using gpasswd a someuser src. Next Im using
> > > Tortoisecvs to login as someuser and upload to the repository Ive
> > > created. It all goes up ok and this has been working without any
> > > problem for the last 4 days between 5 different users but now all
> of
> > a
> > > sudden all commits preformed by any user are changing the group
> > > ownership away from src to the users group name. Once that
> > happens
> > > other users can no longer overwrite or checkout this data.
> > > (someuser is of course to be replaced by the login name of a real
> > > user on the server.)
> > >
> > >
> > >
> > > Obviously I dont understand a great deal about all the
> configuration
> > > options available in CVS but does any body have any idea what
> might
> > > have changed or how I can get this back to my original
> configuration?
> > >
> > >
> > >
> > > I did do an apt-get update and upgrade over the weekend which
> > > might have something to do with whats happened here but I guess a
> > > good question might be, How do other people set this sort of
> system
> > > up for this kind of use.?
> >
> > Maybe the problem is related to the default "umask" for users?
> >
> > Anyway, I find using CVS via shared files very nasty to maintain.
> >
> > I recommend you set up a CVS pserver (either as daemon or via
> inetd),
> > and force everyone to use the :pserver: protocol to
> checkin/checkout.
> > That way, all the files in the CVS repository are then owned by the
> > "cvs" user, and all file permission problems go away forever.
> >
> > Regards,
> >
> > Simon
> >
>
Reply to: