[ On Wednesday, May 5, 2004 at 10:26:24 (+0100), Keith Refson wrote: ]
> Subject: Fw: need to force username of cvs 'action' when using shared SSH account
>
> I'm making a great efford not to be sarcastic in this response. There's
> a genuine argument to be made h
I'm making a great efford not to be sarcastic in this response. There's
a genuine argument to be made here and I hope that there may be one or
two readers who can be convinced by reasonable debate. I'm not
interested in just having an argument, but in making a case.
Greg Woods wrote:
I just can
Keith Refson writes:
>
> I suspect this attitude may be born of an ignorance of how
> SSH works and what it is capable of.
On the contrary, I know quite well what SSH is capable of. But people
do run CVS without using SSH, you know, and the environment is normally
under the control of the *user*
[ someone wrote: ]
> Subject: Fw: need to force username of cvs 'action' when using shared SSH account
>
> 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, inste
<#part sign=pgp [EMAIL PROTECTED]>
Keith Refson <[EMAIL PROTECTED]> writes:
> "Tim Grotenhuis" <[EMAIL PROTECTED]> wrote:
> > 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,
"Tim Grotenhuis" <[EMAIL PROTECTED]> wrote:
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
