At 13:45 -0500 01.30.2001, Morbus Iff wrote:
>Do you SSH through CVS on the Mac? How? I've been requesting pserver for my
>perl projects on SourceForge, and up until last month, things were happy
>and they responded quickly. But a request for pserver from last December
>still hasn't been pushed through.
Sounds familiar.
I did have it set up so I could do a "proxy" through a local Linux box with
rsh + ssh on the Linux box ... but I don't do that anymore. I've heard
that maccvs will be getting SSH support sometime soon.
Regardless, as far as MacPerl is concerned, you should be able to check out
the source anonymously. Only Matthias and I have write access for it, and
anything else can be done anonymously.
But for other projects, well, here is what I have sent to others about my
experiences using maccvs + rsh -> ssh on a Linux box. I don't know how to
do it with MacCVS Pro.
>This was figured out with the help of sabi on EFNet's #macdev. We use
>rsh to connect to a "proxy" Unix box which then connects remotely to the
>SourceForge CVS server with ssh. Because it uses rsh, it may open your
>proxy box to certain security holes (though it is probably more secure
>than relying on a plaintext password). Also, of course, the data sent
>between your proxy and your Mac will be unencrypted.
>
>1. Create a key using ssh-keygen (if you don't already have one), and
>don't give it a password. Store it in .ssh/identity on the box that
>will be your "proxy" machine.
>
>2. Upload the contents of ~/.ssh/identity.pub (the text file) to
>SourceForge. (See https://sourceforge.net/account/ and the key there.)
>You may have to wait several hours for it to be active.
>
>3. Make sure ssh and cvs are installed on the proxy box.
>
>4. Create a file ~/.ssh/config containing (replace PROJECTNAME and
>USERNAME and CVSHOST with the appropriate values):
>
> Host PROJECTNAME
> HostName CVSHOST.sourceforge.net
> User USERNAME
> Cipher blowfish
>
>5. Create a script called "cvsproxy" on the remote box in /usr/bin (and
>make it world executable):
>
> #!/usr/bin/perl
> system "/usr/local/bin/ssh $ARGV[0] cvs @ARGV[1 .. $#ARGV]";
>
>6. Add your Mac's hostname and USERNAME to your ~/.rhosts file:
>
> mymachost.example.com USERNAME
>
>7. Turn on rsh. For my box, I edit /etc/inetd.conf to include or
>uncomment a line looking like this:
>
> shell stream tcp nowait root /usr/sbin/tcpd in.rshd
>
>Then I go to /etc/rc.d/init.d and type:
>
> ./inet restart
>
>8. Set up maccvs to connect via rsh. Select "Rsh" method (and change
>all your CVS:Root files as needed). Go to the "Ports" preferences and
>check "Check for an alternate server name" and enter "cvsproxy
>PROJECTNAME".
>
>So this should call "cvsproxy" on the remote box with the arguments
>"PROJECTNAME" and whatever other arguments would have been passed to
>"cvs". maccvs just turns around and executes "ssh PROJECTNAME cvs" with
>whatever arguments would have been passed to "cvs". rsh handles the
>flow of the data from there, and it all Just Works.
>
>
>I don't think I missed any steps. Let me know if it doesn't work, if I
>can help with any of it.
>
>
>HOWEVER, there is a big problem with it: rsh seems to be somewhat broken
>in versions of MacCvs following 3.1.4 (as mentioned in other posts). So
>in order to do the above, you really need to use the old MacCvs. If you
>want to use the new MacCvs, you need to request pserver access from the
>SourceForge folks.
--
Chris Nandor [EMAIL PROTECTED] http://pudge.net/
Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
