mailing list archives
Re: Status report #1 of 17
From: David Fifield <david () bamsoftware com>
Date: Mon, 27 Apr 2009 22:36:25 -0600
On Tue, Apr 28, 2009 at 04:46:25AM +0530, venkat sanaka wrote:
My name is venkat sanaka,one of the Gsoc 2009 student.I am pursuing my
3rd year B,E,(Hons) Computer science at Bits-pilani,Goa campus
in India.I will be working as a feature creeper/Bug wrangler this summer.
* worked with my mentor on getting svn working through proxy server as i
was behind a proxy server in my college and nmap repository doesnt
support http protocol.Finally got it worked using ssh portforwading
though this method had minor problem with svn-externals.Any further
help on using svn behind proxy perfectly would be appreciated.
The problem we are facing here is that the firewall or proxy server at
Venkat's university for some reason doesn't allow him to connect to
svnserve. This is only a temporary problem until the term is over but it
would be nice to have a solution.
Venkat tried SSH port forwarding through a machine that is not subject
to the firewall, and that works fine for checking out
svn://svn.insecure.org/nmap as svn://ssh-server:8888/nmap or whatever.
The problem is the externals, nbase, nsock, ncat, and zenmap. Once /nmap
is retrieved, those are mapped directly to svn.insecure.org and they get
caught by the firewall again. He worked around the problem temporarily
by editing the externals definitions to point to the SSH server, but if
he commits, that change will go in the repository.
One thing I can think of is that you can set up the port forwarding as
before, and edit your /etc/hosts with an entry like
where <ip> is the address of the SSH server. That's a pretty nasty hack.
Any other ideas?
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org