[Cvsnt] Re: - WinCVS 18.104.22.168 doesn't support a proxy
gustav at morpheus.demon.co.uk
Sat Jun 8 14:07:07 BST 2002
Tony Hoyle <tmh at nothing-on.tv> writes:
> Proxy support relied on buggy & misconfigured proxies... on any properly
> configured site it wouldn't work anyway.
I don't know whether my organisation's firewall is buggy or
misconfigured. However, I don't have any access to the network
specialists who set it up, so I can neither ask, nor can I ask for
changes to allow CVS access (I would almost certainly be unable to put
a convincing case for requiring the access, anyway). So WinCVS 1.2 is
the only way I have of getting access to external CVS repositories.
> It's not really a function of cvs to bypass firewalls, especially
>the way it was done. If you want to do that use another program to
>create a tunnel (preferably encrypted) or wait for someone to write a
>transport that works over XML or something.
Nevertheless, WinCVS 1.2 works *for me* and WinCVS 1.3 does not. If
cvsnt isn't going to support proxies, I either have to stick with
WinCVS 1.2, or ask if it would be possible for WinCVS 1.3 to go back
to its previous CVS version.
If cvsnt is not going to support proxies, can you suggest a (pure
client side) program which will act as a tunnel, as you suggest? It
cannot require any changes on either the firewall, or on the CVS
server at the other end (as I have no way of getting such changes
made). Effectively, a separate program implementing the tunnelling
that (the CVS supplied with) WinCVS 1.2 implements internally...
It would be nice if this problem did not exist, but unfortunately, it
does. And not just for me. I have personally been unable to contribute
effectively to at least one Open Source project because of filewall
issues and CVS (I wan't aware of WinCVS at the time :-(), and I know
that other developers on the same project were also affected. [Luckily
(!) the project in question moved away from using CVS because of this
Cvsnt mailing list
Cvsnt at cvsnt.org
More information about the cvsnt