Archives

All posts for the month July, 2009

Subversion is an open-source version control system. Using subversion you can record the history of source files and directories. It manages file and directories over time. A tree of files is placed into a central repository. The repository is much like an ordinary file server, except that it remembers every change ever made to files and directories.

Creating a Self-Signed Certificate:-

Installing the Certificate:-

You can install the key file server.key and certificate file server.crt, or the certificate file issued by your CA, by running following commands at a terminal prompt:

$ sudo cp server.crt /etc/ssl/certs$ sudo cp server.key /etc/ssl/private
Now simply configure any applications, with the ability to use public-key cryptography, to use the certificate and key files. For example, Apache can provide HTTPS.
To configure Apache for HTTPS add the following three lines to the /etc/apache2/sites-available/subversion file
SSLEngine on
SSLCertificateFile /etc/ssl/certs/server.crt
SSLCertificateKeyFile /etc/ssl/private/server.key
Configure Apache Server (https) the Repository:-
We need to be sure the right modules are enabled

$ a2enmod dav

$ a2enmod dav_svn

We must set up virtual host for subversion server. File that you can put in /etc/apache2/sites-available/default (original file).so we can copy the original file (default) to duplication file (subversion).

$ sudo vim /etc/apache2/mods-available/dav_svn.conf

<Location /repos> DAV svn SVNPath /home/svn/repos AuthType Basic AuthName "Subversion Repository" AuthUserFile /etc/apache2/dav_svn.passwd Require valid-user SSLRequireSSL </Location>User authentication:-
To add the first user, you can run the following command:
$ sudo htpasswd -c /etc/apache2/dav_svn.passwd sureshNote: If you have just installed SVN, the passwd file will not yet exist and needs to be created using the "-c"switch. Adding any users after that should be done without the "-c" switch to avoid overwriting the passwd file.
Direct repository you can run the following command:
$ sudo svn co file:///home/svn/repos
You should start apache service
$ sudo /etc/init.d/apache2 start

The Network passwords by saved , if u save the password in the dialog box.. u can view the setting in the follwoing location

Click Start and open Run
In that window type: control userpasswords2
Press OK
in the next window go to the secon tab on top, named: Advanced
and from there open: Manage Passwords
There you should see if there is a password stored for the address that you have mentioned
If yes then delete it and close the windows with OK
try to connect again to that address, it should prompt for authentication. Do not check the Remember option…

You will see a Policy list to your right. Browse to the Policy “Network access: Do not allow storage of credentials or .NET Passports for network authentication”. Double click it, select Enabled, click Apply and then OK.

Apache references the .htaccess file in web document directories for access control information and other uses. A simple configuration allows password protection with multiple username/password combinations.

In the directory to be protected, create a .htaccess file with contents like this:

AuthType Basic

AuthUserFile /safe/dir/htpasswd

AuthName “Text displayed in popup”

require valid-user

There are many other options for .htaccess, but these are basic password related options to get started. The AuthUserFile refers to a fully qualified file that should not be in the web server document directories. The htpasswd file can be named anything, there can be multiple files storing passwords for .htaccess, and each can be shared for use in multiple directories.

To create the first and second user/password pairs, use:

htpasswd -cb /safe/dir/htpasswd user1 password1

htpasswd -b /safe/dir/htpasswd user2 PaSsWoRd2

Additional user/password pairs can be added using the second form. Be certain to protect the htpasswd file.