Message from discussion
passwd
Received: by 10.68.227.67 with SMTP id ry3mr10655819pbc.8.1341237035277;
Mon, 02 Jul 2012 06:50:35 -0700 (PDT)
Path: l9ni9878pbj.0!nntp.google.com!news1.google.com!news.glorb.com!usenet.stanford.edu!not-for-mail
From: "Zhao, Jing" <Jing.Z...@ChasePaymentech.com>
Newsgroups: gnu.cvs.help
Subject: RE: passwd
Date: Mon, 2 Jul 2012 09:50:14 -0400
Lines: 121
Approved: info-...@nongnu.org
Message-ID: <mailman.3872.1341237034.855.info-cvs@nongnu.org>
References: <BF22B2C8BC9A0B4A8875F088CDDDC9DF5B26B4@2ksrvr0a.march-hare.local>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
X-Trace: usenet.stanford.edu 1341237034 23702 208.118.235.17 (2 Jul 2012 13:50:34 GMT)
X-Complaints-To: action@cs.stanford.edu
To: 'Arthur Barrett' <arthur.barr...@march-hare.com>, "info-...@nongnu.org"
<info-...@nongnu.org>
Envelope-to: info-...@nongnu.org
X-IronPort-AV: E=Sophos;i="4.77,511,1336366800"; d="scan'208";a="19998039"
X-IronPort-Term-List: On
Thread-Topic: passwd
Thread-Index: Ac1WCxuGYguMwEoQQGO16IhYXJh39QAY0CsAAHp4WgA=
In-Reply-To: <BF22B2C8BC9A0B4A8875F088CDDDC9DF5B26B4@2ksrvr0a.march-hare.local>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
recognized.
X-Received-From: 206.253.186.152
X-BeenThere: info-...@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Announcements and discussions for the CVS version control system
<info-cvs.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/info-cvs>,
<mailto:info-cvs-requ...@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/info-cvs>
List-Post: <mailto:info-...@nongnu.org>
List-Help: <mailto:info-cvs-requ...@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/info-cvs>,
<mailto:info-cvs-requ...@nongnu.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Arthur,=20
Thank you very much for your detailed info. I use CVS1.11.21. We cannot use=
gserver, sspi or ssh for authentication with a lots of reasons I don't wan=
t to explain it in details. =20
CVSROOT/passwd is fine for us. Just want to simplify our process and elimin=
ate 'step 5' or replace 'step 5' with some kind of cvs command. =20
BTW, CVS1.11.21 works very well.=20
Really appreciated your help. =20
Jing =20
-----Original Message-----
From: Arthur Barrett [mailto:arthur.barr...@march-hare.com]=20
Sent: Friday, June 29, 2012 11:21 PM
To: Zhao, Jing; info-...@nongnu.org
Subject: RE: passwd
Hi Jing,
Your question is more complex that it first appears.
i) the answer depends on which version of CVS server and client you are usi=
ng, and potentially the operating system of each. Eg: CVSNT 2.8.01 on Red =
Hat Linux server is different to CVS 1.11.
ii) there are several different authentication protocols - the most secure =
do not use any passwords sent in clear text like passwd/pserver does. Eg: =
gserver, sspi, ssh (with keys), sserver (with keys) etc. For 'native' auth=
entication you don't 'add users' to cvs, you add them to the host operating=
system. Depending on the version of CVS you may be able to use CVSROOT/pa=
sswd to 'restrict' access to CVS to some host users.
iii) the passwd file is primarily used by pserver protocol. Generally as a=
rule of thumb, the pserver protocol is insecure and rarely recommended.
iv) if you are using pserver, you can use 'native' authentication (again no=
need to add anything to CVSROOT/passwd) using SystemAuth=3Dyes in CVSROOT/=
config or you can use non-native authentication using CVSROOT/passwd
v) if you are user pserver, with non-native authentication and CVS 1.11 the=
n you can either add passwd directly to the CVSROOT directory in the server=
, or you can 'checkout' CVSROOT and add passwd to 'checkoutlist'
and the CVSROOT directory and 'commit' it. To generate the passwords
you'll need some tool that generates linux passwords.
vi) if you are user pserver, with non-native authentication and CVSNT
2.5 or later on linux or windows then you can use 'cvs passwd' from the cli=
ent or the server.
Implementing CVS well takes some work - I recommend you get a good book on =
the subject from Amazon or your favourite technical books seller. I had a =
hand in writing 'All About CVS' or there is the ever popular 'Essential CVS=
' or many many others.
Regards,
Arthur Barrett
=20
> -----Original Message-----
> From:=20
> info-cvs-bounces+arthur.barrett=3Dmarch-hare....@nongnu.org
> [mailto:info-cvs-bounces+arthur.barrett=3Dmarch-hare.com@nongnu.
> org] On Behalf Of Zhao, Jing
> Sent: Saturday, 30 June 2012 1:23 AM
> To: 'info-...@nongnu.org'
> Subject: passwd
>=20
>=20
> Could you shed some light on how to add new user to cvs repository?=20
> This is what I do as follows:
>=20
> 1. cvs co CVSROOT
> 2. cd CVSROOT
> 3. vi passwd # add new users
> 4. cvs ci -m "adding xxxx"
> 5. I have to physically login to CVS repository server, go to CVSROOT=20
> directory, then drop this latest passwd file over there, otherwise, it=20
> would not work.
>=20
> Is there any command to eliminate step 5? I checked 'cvs admin'=20
> command, I did not see how to do that.
> Appreciate you any help.
>=20
> Jing
> ----------
> Learn more about Chase Paymentech Solutions,LLC payment processing=20
> services at www.chasepaymentech.com.
>=20
> THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments=20
> are proprietary and confidential information intended only for the use=20
> of the recipient(s) named above.
> If you are not the intended recipient, you may not print, distribute,=20
> or copy this message or any attachments. If you have received this=20
> communication in error, please notify the sender by return e-mail and=20
> delete this message and any attachments from your computer.
>=20
>=20
>=20
>=20
----------
Learn more about Chase Paymentech Solutions,LLC payment processing services=
at www.chasepaymentech.com.
THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are =
proprietary and confidential information intended only for the use of the r=
ecipient(s) named above. If you are not the intended recipient, you may no=
t print, distribute, or copy this message or any attachments. If you have =
received this communication in error, please notify the sender by return e-=
mail and delete this message and any attachments from your computer.