Re: can't track users that check-in remotely via ssh

[Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code 6067]

Mark wrote, On 07/26/2007 11:03 AM:
> Todd Denniston wrote:
> > Mark wrote:
> >
> > > I like to use a remote machine to do cvs check-ins because I
> > > have management control on it and so I have installed better
> > > tools (compilers, editors, etc). But when I check in to
> > > our cvs server, because I'm going through ssh remotely
> > > this is typical of what goes in the commitlog:
<SNIP>
> > > This is on cvs 1.9 as the cvs server and cvs 1.11.22 as the
> > > remote client.
> > >
> > > Mark
> >
> > I am also using ssh.
> >
> > 1) have you considered updating to something a little more secure on 
> > the server? I mean there have been a huge number of security fixes 
> > since 1.9 came out.
>
> I don't have admin control over that server. Eventually they'll replace 
> that machine because it's getting kind of old. I'm sure
> it will be updated (or whatever replaces it will).

Sometimes asking nicely, or pointing out to the admin/boss that there are 
probable security problems, will get a machine updated.
Also you could either ask, or subvert the system yourself, to have another CVS 
set installed, i.e., have someone compile up CVS with 
--prefix=somewhere_else_like_a_home_dir
and then on your clients set the equivalent to
CVS_SERVER=somewhere_else_like_a_home_dir/bin/cvs
then your project will be using the new one.
I have used this subversion each time I updated CVS on a Sun machine, so that 
I and I alone tested the new version until I was happy with it (Suns are 
tricky sometimes).


> > 2) the modern commit_prep and log_accum (mine came from cvs-1.11.19) 
> > puts the username at the beginning of the message. [for use with 
> > commitinfo]

BTW these can be used with out updating the CVS binary itself, they are 
repository specific.

> > 3) why do you really care who committed what in the commit log files, 
> > when you can query the repository directly if you really need to know?
>
> Yes, doing a cvs log on the files works too but the CVSROOT/commitlog is 
> a global list of events, it's very convenient for looking quickly
> at what's happened recently (time ordered too which is nice) than
> having to go to each file with cvs log.

For time ordered, May I also suggest looking at cvs2cl?
I usually run it as:
cvs2cl -r -t
http://www.red-bean.com/cvs2cl/

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter