I think it would be absolutely great to integrate HTTP
Proxy Support to Tortoise.So that you can connect to
CVS Servers also when you are in an internal Network
and Internet is only available through a Proxy
I don't know if it's possible ... but it would be amazing.
Logged In: YES
user_id=629477
CVS connects directly via TCP/IP, not through HTTP. HTTP
uses TCP port 80, CVS usually port 2401. So HTTP proxies
are not relevant for CVS. And as far as I know, there is no
such thing as a CVS proxy. If you are behind a firewall and
cannot connect to a CVS server, all you can do is ask your
network security administrator to open up port 2401 for you.
Logged In: YES
user_id=788825
You are right ... but take a look at PuTTY (if you do not
know it, it's ssh client,
http://www.chiark.greenend.org.uk/~sgtatham/putty/) which
can connect to open ssh ports via a proxy. Or do you know
Trillian? It connects to icq servers via proxys ... As i
said I don't know if it's possible, but when a ssh client
has this feature why should here be no possibility for it?
Logged In: YES
user_id=629477
Sorry, I wasn't aware that HTTP proxies could be used to set
up a tunnel to ports other than HTTP ports.
Proxy support is more a CVS feature than a TortoiseCVS
feature though. And there was a discussion on the CVSNT
mailing list some time ago:
http://www.cvsnt.org/pipermail/cvsnt/2002-June/002433.html
They mention some programs that can setup tunnels through
HTTP proxies - maybe you should try them. Essentially what
you'd have to do is us those one of those tools to setup a
tunnel between a local TCP port (let's say 1234) on your
machine and the CVS port (usually 2401) on the remote
machine. Once that tunnel is set up, you should be able to
specify "localhost" as server and "1234" as port for the
CVSROOT you want to use.
If you succeed in connecting through an HTTP proxy, feel free
to share the details on the TortoiseCVS users mailing list.
We could integrate it into our FAQ then.
Logged In: YES
user_id=788825
imho it would be a very great feature ... and i think i'm
not the only one who would use it. If you're not sure, make
a poll ;o)
I don't know how much time it would take ... but it hasn't
to be realized for tomorrow, and i think it couldn't be so
difficult....
Nice Greetings ...
Logged In: YES
user_id=91098
You see, the whole internet will be running over Port 80 by
the year 2010, I tell you ;)
Seriously, if your network administrator is happy for you to
access CVS proxied over port 80, then he ought to be happy
with you accessing it over port 2401. Otherwise he is being
inconsistent with his security policy, as both are equally
secure.
Or are you trying to get round the wishes of your network
administrator? In practice I believe you want the network
to route round your administator, because it is too much
hassle to persuade him to open the port. Which is fair
enough, but understand the consequences of this. It's an
arms race, he'll be filtering port 80 soon, just you watch.
Then you'll be tunneling CVS protocol masquerading as HTML
over port 80, and so on.
Finally, Subversion (the successor to CVS which is nearly at
1.0) uses WebDAV stuff and port 80 by default. See, whether
you like it or not, everything will be over port 80 some
time soon...
Logged In: YES
user_id=146867
Our network admins don't care what it is as long is it comes
and goes through port 80 and a small handful of others like
22 (usually for SSH). It doesn't look like sourceforge is
going to offer :pserver: access over SSH anytime soon.
However there is the webserver cvs access, could Tortoise be
set up to use that instead when port 2401 is unavailable?
I'm currently using a package called cvs-grab for this. It
functions for the most part when downloading a new module
but often can't handle individual changed files very well. I
would love to be able to use a single CVS-checkout tool
(Tortoise) instead of the current grab-bag of duct-taped
together tools... :)
http://cvsgrab.sourceforge.net/
cheers,
-matt
Logged In: YES
user_id=91098
I know this answer is going to irritate you, but it is
true, so I'm going to say it anyway. If your network admin
doesn't care what goes across the network, as long as it is
on port 80, then they are being foolish. Port 80 isn't
magically more secure than any other port, whatever
protocol is on it.
Allowing you to open /outgoing/ pserver connections would
not compromise their network security, any more than you
using CVSGrab to download the files. Of course this is no
help to you if you have no influence over your network
administrator.
In the case of Putty and Trillian, do you know what kind of
proxying they are using? Be precise - is it one of the
weird fancy protocols, (WinSocks proxy?). If so which one?
Other than that, you say you are allowed to use SSH. If
so, you can check out modules using SSH from SourceForge.
You may even be able to do that read-only without being a
developer on the project. And TortoiseCVS can do it very
well.
Logged In: YES
user_id=146867
Agreed; however I have no influence on the firewall policies.
I have not been able to find a way to do that. It would
certainly solve my problem, and likely impose a lesser load
on the sourceforge servers as well. If you or anybody else
can point to some docs on anonymous read-only SSH cvs access
to SF I will happily turn my brain to mush in an attempt to
understand them.
-matt
Logged In: YES
user_id=91098
Rats, you can't. You need to be a developer to use SSH
checkout. Just tried it - even the switch -R which looks
like it should help doesn't work.
You could add a feature request to integrate CVS Grab intto
TortoiseCVS, I guess. It would make sense - it is only for
getting read only, and you only need it for read only.
Logged In: YES
user_id=1106788
Wouldn't it be easiest to use the proxy-command line syntay
of CVSNT client itself??? IIRC you just need to specify
pserver;proxy=addr;poxyport=port:user@server:port/root to
use with proxies with CVSNT. It shouldn't be TOO difficult
to add two edit boxes to enter the proxy host and port and
filter this information in the config string.