Subversion (SVN) is a version control system designed to be the successor of CVS (Concurrent Versions System). The concept is similar to CVS, but many shortcomings where improved. See also the SVN book. Server setup The initiation of the repository is fairly simple (here for example /home/svn/ must exist): # svnadmin create –fs-type fsfs /home/svn/project1
Server setup Initiate the CVS Decide where the main repository will rest and create a root cvs. For example /usr/local/cvs (as root): # mkdir -p /usr/local/cvs # setenv CVSROOT /usr/local/cvs # Set CVSROOT to the new location (local) # cvs init # Creates all internal CVS config files # cd /root # cvs checkout CVSROOT
So called SSL/TLS certificates are cryptographic public key certificates and are composed of a public and a private key. The certificates are used to authenticate the endpoints and encrypt the data. They are used for example on a web server (https) or mail server (imaps). Procedure We need a certificate authority to sign our certificate.
There are (many) other alternative methods to encrypt disks, I only show here the methods I know and use. Keep in mind that the security is only good as long the OS has not been tempered with. An intruder could easily record the password from the keyboard events. Furthermore the data is freely accessible when
OpenSSL A single file Encrypt and decrypt: # openssl aes-128-cbc -salt -in file -out file.aes # openssl aes-128-cbc -d -salt -in file.aes -out file Note that the file can of course be a tar archive. tar and encrypt a whole directory # tar -cf – directory | openssl aes-128-cbc -salt -out directory.tar.aes # Encrypt #