Thank You for All your Help... It worked flawlessly (meaning it worked
right the first time).  

> On Wed, 2003-09-17 at 09:39, Mark Gardner wrote:
> 
>>Well that would work but I don't have another machine I can setup as a
>>dedicated sourceforge server.  I heard somewhere that you can setup
CVS
>>to use SSH and then the folder permissions will allow/disallow the
>>viewing of other peoples code.
> 
> 
> Yup.  Just set the env variable CVS_RSH=ssh and everything will go
over
> ssh.  make your CVSROOT look something like this:
> 
> [EMAIL PROTECTED]:/home/torriem/cvsroot

:ext:[EMAIL PROTECTED]:/home/torriem/cvsroot to be more specific, which

may be necessary on some platforms.

This should also work in Windows (if you must) if you have the cvs.exe 
from cvshome.org and either ssh.com's ssh2.exe (CVS_RSH="C:\Path to 
SSH\ssh2.exe")or putty. If you use putty you'll _have_ to use public key

auth and pageant because plink doesn't play nice with cvs (or anyone 
else for that matter). ssh.com's ssh2.exe will work exactly like ssh in 
linux.

You could also use cygwin's openssh, but I'd recommend the native win32 
binary of cvs anyway (not cygwin) because the native binary will convert

line-ends back and forth for you (so that they're always in Unix mode on

the server, but are always in DOS mode on the client). Or just use 
cygwin all the way. That also works.

(For those of you annoyed that I went into windows detail, Mark asked me

in person to remind him what the windows quirks were.)
> 
> For permissions, if you create a new secondary group, add all you
users
> to it, and then make your repository folder be setgid (chmod g+s
> folder), then all writes to it by group members will be owned by that
> group.  Just make sure the file is group writable.

____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to