subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Canfield <andy.canfi...@pimco.mobi>
Subject Re: Subversion access control
Date Sat, 23 Jul 2011 09:55:30 GMT


On 07/22/2011 02:39 AM, Ryan Schmidt wrote:
> On Jul 20, 2011, at 23:14, Andy Canfield wrote:
>
>> I would like to use http/https. I am not supposed to be working on the server, but
on my notebook workstation. And svn or svn+ssh require port 3690 to be forwarded by the router,
and we don't own the router. So I would prefer http and/or https.
> First of all, svn:// protocol uses port 3690, yes (or whatever port svnserve is listening
on), but svn+ssh:// protocol uses port 22 (or whatever port sshd is listening on).
>
> Second, what does a router have to do with this? You can't access the server directly
from the client? You have to go through a router's port forwarding?
>
Yes.

Ten years ago I read that an unprotected Windows computer, connected 
directly to the Internet, would become infected within two minutes. In 
the years after that surprising statement came to realize that I have 
never seen a Windows computer directly connected directly to the Internet.

WIth my own eyes I have never seen ANY computer connected directly to 
the Internet. Every server computer accessable from the internet that I 
have ever laid eyes on is connected via a router which forwards packets 
to the server. Usually it goes ADSL / router / LAN / server and we use 
Dynamic DNS to make it accessable from the Internet. In this case, 
however, they paid the money and the ISP delivered a fixed Internet IP 
address and a router. I send a packet to port 80 and it goes to the 
router and gets forwarded to the server which replies. I send a packet 
to port 3690 and the router just drops it. Since the router is owned by 
the ISP we do not have the admin password. We have a request in to 
forward port 3690 but it hasn't been done yet.

Interesting that svn+ssh uses port 22. I know that port 22 is working; I 
go in to the server all the time using ssh and sftp. I should look into 
that.


Mime
View raw message