Censorship banner.png

Difference between revisions of "Tecnico:Svn+ssh"

From Wiki - Hipatia
Jump to: navigation, search
m (Requirements)
m (Abstract)
Line 2: Line 2:
 
== Abstract ==
 
== Abstract ==
 
When setting up a freely accessible Subversion repository, we decided to make it available over http (using[[Guri:Latex_and_Subversion | Apache and WebDAV]]). This method offers the possibility for any user to browse our projects through a web browser. To avoid spam, we decided to grant to every anonymous user the permission to checkout the repository, but we are currently requiring authentication to commit files and changes.  
 
When setting up a freely accessible Subversion repository, we decided to make it available over http (using[[Guri:Latex_and_Subversion | Apache and WebDAV]]). This method offers the possibility for any user to browse our projects through a web browser. To avoid spam, we decided to grant to every anonymous user the permission to checkout the repository, but we are currently requiring authentication to commit files and changes.  
With our current configuration we are facing two problems:
+
With our current configuration the connection between the subversion client and the repository is not encrypted
* the connection between the subversion client and the repository is not encrypted
 
* the passwords are stored in plain text on the filesystem.
 
  
This paper explains how to fix such problems, in the case in which SSL usage is not possible. The answer to this is running a custom ''svnserver'', providing encrypted svn repository access over an ssh tunnel.
+
This paper explains how to fix such problem, in the case in which SSL usage is not possible. The answer to this is running a custom ''svnserver'', providing encrypted svn repository access over an ssh tunnel.
  
 
== Authentication ==
 
== Authentication ==

Revision as of 10:28, 12 October 2011

The help pages are provided by Hipatia volunteers to help wiki contributors.
Help index: Mediawiki Server configuration LaTeX Streaming Templates

Search for help:


Abstract

When setting up a freely accessible Subversion repository, we decided to make it available over http (using Apache and WebDAV). This method offers the possibility for any user to browse our projects through a web browser. To avoid spam, we decided to grant to every anonymous user the permission to checkout the repository, but we are currently requiring authentication to commit files and changes. With our current configuration the connection between the subversion client and the repository is not encrypted

This paper explains how to fix such problem, in the case in which SSL usage is not possible. The answer to this is running a custom svnserver, providing encrypted svn repository access over an ssh tunnel.

Authentication

Requirements

This paper assumes that you already have access to a working server, providing ssh connection, with subversion repositories already existing and running. There are many methods to make a subversion repository accessible via ssh. Depending on the one you choose, there are different requirements.