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

[Mark]

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:
> >
> > project/demo/src frontside.cc
> > Mon Jul 23 10:36:40 EDT 2007
> > Update of /repo/projectcvs/main/project/demo/src
> > In directory cvshost.domain.org:/tmp/cvs-serv6345/src
> >
> > Basically the negative side of doing remote cvs checkins
> > is that commitlog file tracking who did what checkin is getting
> > sanitized by that ambiguous "cvs-serv####" string
> >
> > When I check-in locally I can tell it was me because
> > my sandbox is under my home directory so my home
> > directory name is embedded in the "In directory" path.
> >
> > Is there some way to get remote entries in the log to embedded the
> > ssh username?  Maybe it could look like:
> >
> > project/demo/src frontside.cc
> > Mon Jul 23 10:36:40 EDT 2007
> > Update of /repo/projectcvs/main/project/demo/src
> > In directory cvshost.domain.edu:address@hidden:/tmp/cvs-serv1113/...
> >
> > or instead of that number #### can cvs use append the username
> > to that:   /tmp/cvs-serv1113_user ??
> >
> > 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).

> 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]
>
> 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.

Mark