[P]Delete

To learn more about HAProxy I decided to compile it from source and use it to load-balance traffic to louwrentius.com across two different web servers. I run HAProxy on a VPS based on Ubuntu 12.04 LTS. Let's dive right in. First, we need to download the source. Don't copy/pased the exact code, you should download the latest version of HAProxy. cd /usr/src wget "http://haproxy.1wt.eu/download/1.4/src/haproxy-1.4.24.tar.gz" tar xzf haproxy-1.4.24.tar.gz cd haproxy-1.4.24 Before you can compile software, you must make sure you have a working build-environment. With Ubuntu or Debian, you should run: apt-get install build-essential If you open the README file in the root directory, you will find some detailed instructions on how to compile HAProxy, which is really straight-forward. Compiling HAProxy Best CPU performance The manual states that by default, it will compile HAProxy with no CPU-specific optimisations. To enable CPU-specific optimisations, you n

Introduction: Bacula is an on-linebased back up tool. Which is used to backup files from different servers into back up server where the bacula is running. For setup this backup tool across network first you have to install bacula server package on backup server machine where you are storing your backup contents ,and install bacula client daemon on all other servers from where we are going to backup data. Bacula has five main components. 1.Director daemon This daemon co-ordinate all working of backup,and through its configuration file we can specify all these things. 2.File daemon This daemon works in all clients from that client we are backup data. Director daemon connect to this daemon after authentication and backup the files from this client. 3.Storage daemon This daemon is for store the backup data from client in to hard disk of backup server,usually this daemon and director daemon works in the same backup server. director works as intermediate between the file

Software Requirements To deploy Forward Secrecy, you need to have both your web server and the underlying SSL/TLS library support Elliptic Curve cryptography. For Apache, Nginx, and OpenSSL, the following minimum versions will suffice: OpenSSL 1.0.1c+ Apache 2.4.x nginx 1.0.6+ and 1.1.0+ You will probably want to upgrade to the most recent versions wherever possible, because you don’t want to be running old and obsolete and potentially vulnerable software. You are probably aware that Linux distributions often ship modified packages. The modifications are usually improvements, but could mean feature removal in some cases. For example, Red Hat appears to have no support for Elliptic Curve crypto on their operating systems, because of  patent issues . If you’re running CentOS, for example, and wish to support Forward Secrecy, you will need to recompile the key packages to put EC support back in . (There appear to be plenty tutorials on the Web for this.) Once the correct pac

To encrypt communications between you and your end users, you purchase a SSL Certificate, install it on your server, and then configure your website to use the certificate to protect these communications. The SSL connection begins when the end user’s browser reaches out to shake hands with your website. During this handshake, information regarding the ability of the browser and server are exchanged, validation occurs, and a session key that meets both the browser’s and server’s criteria is created. Once the session key is created, the rest of the conversation between the end user and your site is encrypted and thus secured. Historically, the most common method for negotiating the session key involved the RSA public-key cryptosystem. The RSA approach uses the server’s public key to protect the session key parameters created by the browser once they are sent the server. The server is able to decrypt this handshake with its corresponding private key. When you use the RSA key exchange