This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: CVS using a proxy ?
- To: richard dot earnshaw at arm dot com
- Subject: Re: CVS using a proxy ?
- From: Jim Kingdon <kingdon at cyclic dot com>
- Date: Sat, 18 Jul 1998 14:57:01 -0400
- CC: hans-peter dot nilsson at axis dot com, nicolas at bnp-eng dot remcomp dot com, egcs at cygnus dot com, larry dot jones at sdrc dot com, rearnsha at sun52 dot arm dot com
- References: <199807181807.TAA24493@sun52.NIS.cambridge>
> But there is no need to use a special (socksified) variant of cvs.
> For machines that support dynamic linking there is a script that comes
> with socks that allows you to change the inet protocol stack used at
> run time.
In my opinion this approach, and/or something else which allows one to
one to change authentication details at run-time without having to
patch CVS, is the way to go.
This is partly just because I am a lazy application writer and don't
want to have to update my application for the 3 zillion different
authentication/connection schemes out there. But it is also The Right
Thing(TM) for network security -- you don't want the security of your
network to be at the mercy of whether CVS (and every other
application) has gotten things right.
I've updated the SOCKS information at
http://www.cyclic.com/cvs/dev-net.html to suggest runsocks.