> > > > Is there a reason why you can't use the old-fashioned strategem > > of one account per developer ?
My ISP won't give me additional accounts. > > You can also use $HOME/.ssh/environment on the client side to tunnel > > environment variables of your choice. I've never tried it myself, I > > just saw that in the ssh man page. (Your developers would be able to > > cheat, though.) The trouble is, CVS doesn't look at the environment to > > decide who's calling. My script that runs in the command="" option in the authorized_keys2 file runs successfully and I can control the input based on which key (ie, which developer) is used. I am looking for the correct environmental variable that CVS WILL look at. > > > > > There HAS to be a way to force cvs to record the correct committer > > > name. > > > > Why ? Why would cvs extract that information from a source other than > > its own euid ? I just can't imagine that this hasn't been required before: a single shell account with a used id of, for example, 'cvsuser' requiring SSH, instead of pserver, authentication and access for developers. The nature of CVS, that of tracking diffs and who did what when, seems to be compromised in this situation. Thats all. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
