Re: [Savannah-dev] what is proski actually doing?

[Jaime E. Villate]

Hi Nic,
No, proski is not a cracker and he is doing the most clever thing to do (in my
opnion) and what I have always told Savannah users to do when they can't
connect via cvs.

The commands
   export CVS_RSH=ssh
   cvs -d address@hidden:/cvsroot/project co .
open a ssh server anyway, which is perfectly normal usage; by giving users an
account we are allowing them to use a shell; in this case the cvsshell.

If the commands above fail, the best advice we can give users is to try that
ssh command proski tried. The final result should be a message from the
cvsshell saying that the user should provide one of the few commands it
understands.

In proski's case cvsshell did not respond, which shows that he is not being
given access to subversions. The ssh key was apparently accepted, so there is
some other authentication problem; my guess is that ssh has detected some
security problem (for instance a .ssh directory with wrong permissions) and
has closed the connection. But I will have to investigate that problem better.

The other cvs command that proski showed us in hs support task is equivalent
to the one proposed on the Savannah page, and from its output it is clear that
he has already set CVS_RSH correctly.

Cheers,
Jaime

On Tue, Oct 15, 2002 at 10:45:16PM +0000, Nic Ferrier wrote:
> Are we sure that proski isn't just some cracker?
> 
> The command:
> 
>    ssh -1 -v subversions.gnu.org cvs server
> 
> which he is complaining about not working is used to start a new cvs
> server running on subversions.
> 
> Maybe he's trying that innocently... maybe he's not.
> 
> We should be careful with him I think.