[lug] cvs pserver

[Riggs, Rob]

I'll second the SSH recommendation. CVS pserver is far too insecure. I also
find it more difficult to manage.

I also agree with the second point. I've set up CVS pserver before and have
no clue why it would want /root to be world readable. I have never seen that
before.

-----Original Message-----
From: Atkinson, Chip [mailto:CAtkinson at Circadence.com]
Sent: Wednesday, April 25, 2001 10:45 AM
To: 'lug at lug.boulder.co.us'
Subject: RE: [lug] cvs pserver


We are using cvs with W2K clients and using ssh authentication.  I didn't
like pserver because of having clear text passwords going across the LAN.  I
used the cygwin version of ssh and was able to get through it all and have
it working.

You might wish to investigate that option.  I tried pserver for a bit and
never had the .cvsignore problem that you mention.

I can help you with the ssh stuff a bit though.
Chip

> -----Original Message-----
> From: D. Stimits [mailto:stimits at idcomm.com]
> Sent: Wednesday, April 25, 2001 10:39 AM
> To: BLUG
> Subject: [lug] cvs pserver
> 
> 
> I'm trying to get my internal net working with cvs using pserver, and
> one thing keeps frustrating me about it. Apparently I *must* make the
> /root/ world readable so that it can read /root/.cvsignore, which I
> refuse to do. Does anyone know if there is a way to force it 
> to instead
> use something like /etc/cvsignore instead? Does anyone here have cvs
> working with networked clients such that /root/.cvsignore can 
> be blocked
> out of permissions?
> 
> D. Stimits, stimits at idcomm.com
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug