Ubuntu/apache2 - Revision history

R00t: /* Hardening */

2016-01-21T04:03:27Z

‎Hardening

2016-01-21T03:52:46Z

‎Disable options through virtual site conf

2016-01-21T03:50:35Z

‎Hardening

2016-01-21T03:42:27Z

‎Hardening

2016-01-21T03:30:53Z

2016-01-21T03:29:29Z

2016-01-21T03:26:29Z

2016-01-21T03:25:37Z

2015-11-29T22:31:08Z

2015-11-29T22:30:43Z

@@ Line 127: / Line 127: @@
 <Directory /var/www/mysite.com/>
                  AllowOverride None
 </Directory></nowiki>

@@ Line 104: / Line 104: @@
 <Directory /var/www/mysite.com/>
                  Options -Indexes -Includes -ExecCGI -FollowSymLinks
 </Directory></nowiki>

@@ Line 115: / Line 115: @@
 <Directory /var/www/mysite.com/>
                  ServerSignature Off
 </Directory></nowiki>

← Older revision		Revision as of 03:42, 21 January 2016
Line 110:		Line 110:
	<nowiki>#Disable SSLv3		<nowiki>#Disable SSLv3
	SSLProtocol All -SSLv2 -SSLv3</nowiki>		SSLProtocol All -SSLv2 -SSLv3</nowiki>
		+
		+	====Hide Apache Version Number====
		+	<nowiki>i.e.
		+	<Directory /var/www/mysite.com/>
		+	ServerSignature Off
		+	</Directory></nowiki>

@@ Line 57: / Line 57: @@
   </nowiki>
 ==mod_authz_host==
@@ Line 99: / Line 94: @@
 ==Hardening==
 Hardening is a must.<br>
 All of the following can be added to a virtual site conf file to harden it by disabling options that have been commonly used as attack vectors:
 *Directory browsing
@@ Line 108: / Line 105: @@
                  Options -Indexes -Includes -ExecCGI -FollowSymLinks
 </Directory></nowiki>

← Older revision		Revision as of 03:29, 21 January 2016
Line 98:		Line 98:

	==Hardening==		==Hardening==
		+	Hardening is a must.<br>
		+	All of the following can be added to a virtual site conf file to harden it by disabling options that have been commonly used as attack vectors:
		+	*Directory browsing
		+	*Server side Includes
		+	*CGI execution
		+	*Symbolic links
		+	<nowiki>i.e.
		+	<Directory /var/www/mysite.com/>
		+	Options -Indexes -Includes -ExecCGI -FollowSymLinks
		+	</Directory></nowiki>

@@ Line 30: / Line 30: @@
 http://httpd.apache.org/docs/current/rewrite/remapping.html<br>
 ====enabling====
 was not enabled by default for my ubuntu 14.04 vm.
@@ Line 71: / Line 63: @@
   SSLProtocol All -SSLv2 -SSLv3
 ==listen on non-standard port==
 On ubuntu 14.04, it is done by adding this:

@@ Line 29: / Line 29: @@
 http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html<br>
 http://httpd.apache.org/docs/current/rewrite/remapping.html<br>
 ====enabling====
 was not enabled by default for my ubuntu 14.04 vm.
@@ Line 85: / Line 94: @@
          Servername https://wiki.r00tedvw.com</nowiki>
 Apparently, it is redundant and will cause issues if you list the hostname in the VirtualHost.  In this instance, I only have (1) site live on the server, so this may not be the correct solution for a multi-tenant setup.

← Older revision		Revision as of 22:31, 29 November 2015
Line 1:		Line 1:
		+	==Basic Info==
	;apache2 is the most popular web hosting application on the market today		;apache2 is the most popular web hosting application on the market today
	<br\>		<br\>

← Older revision		Revision as of 22:30, 29 November 2015
Line 74:		Line 74:
	<nowiki>~$ echo "ServerName localhost" \| sudo tee /etc/apache2/conf-available/fqdn.conf		<nowiki>~$ echo "ServerName localhost" \| sudo tee /etc/apache2/conf-available/fqdn.conf
	~$ sudo a2enconf fqdn</nowiki>		~$ sudo a2enconf fqdn</nowiki>
		+
		+	==SSL Error: Invalid method in request \x16\x03\x01==
		+	I only started having SSL issues after moving to CloudFlare as a proxy so that they would provide me with a free SSL cert. I found that this issue appeared to be due to the fact my Virtual Host site conf was setup as such:
		+	<nowiki>(snippet)
		+	<VirtualHost https://wiki.r00tedvw.com:443>
		+	Servername https://wiki.r00tedvw.com</nowiki>
		+	I changed it to this:
		+	<nowiki> <VirtualHost *:443>
		+	Servername https://wiki.r00tedvw.com</nowiki>
		+	Apparently, it is redundant and will cause issues if you list the hostname in the VirtualHost. In this instance, I only have (1) site live on the server, so this may not be the correct solution for a multi-tenant setup.