Installing Jinzora on Ubuntu - Revision history

Hutch at 21:04, 11 October 2007

Hutch — Thu, 11 Oct 2007 21:04:40 GMT

←Older revision		Revision as of 21:04, 11 October 2007
Line 1:		Line 1:
-	The following are step-by-step instructions for installing Jinzora 2.75 on a Ubuntu 7.04 (Feisty) system. Please visit the [[#Links]] to read more about the installation before proceeding.	+	The following are step-by-step instructions for installing an Jinzora 2.75 on a Ubuntu 7.04 (Feisty) system. Jinzora will be accessed via HTTPS. Please visit the [[#Links]] to read more about the installation before proceeding.

	== Install Jinzora ==		== Install Jinzora ==

Hutch at 21:03, 11 October 2007

Hutch — Thu, 11 Oct 2007 21:03:26 GMT

←Older revision		Revision as of 21:03, 11 October 2007
Line 104:		Line 104:
	$ '''sudo /etc/init.d/apache2 reload'''		$ '''sudo /etc/init.d/apache2 reload'''

-	=== Links ===	+	== Links ==

	* [http://www.linode.com/wiki/index.php/Apache2_SSL_in_Ubuntu Apache2 SSL in Ubuntu]		* [http://www.linode.com/wiki/index.php/Apache2_SSL_in_Ubuntu Apache2 SSL in Ubuntu]

Hutch at 21:00, 11 October 2007

Hutch — Thu, 11 Oct 2007 21:00:06 GMT

←Older revision		Revision as of 21:00, 11 October 2007
Line 1:		Line 1:
	The following are step-by-step instructions for installing Jinzora 2.75 on a Ubuntu 7.04 (Feisty) system. Please visit the [[#Links]] to read more about the installation before proceeding.		The following are step-by-step instructions for installing Jinzora 2.75 on a Ubuntu 7.04 (Feisty) system. Please visit the [[#Links]] to read more about the installation before proceeding.
		+
		+	== Install Jinzora ==

	* Install prerequisites.		* Install prerequisites.
Line 10:		Line 12:
	$ '''sudo tar zxvf jz275.tar.gz -C /var/www/'''		$ '''sudo tar zxvf jz275.tar.gz -C /var/www/'''
	$ '''( cd /var/www/jinzora2 && sudo sh configure.sh )'''		$ '''( cd /var/www/jinzora2 && sudo sh configure.sh )'''
		+
		+	== Configure Jinzora ==

	* Change PHP5 settings for Jinzora.		* Change PHP5 settings for Jinzora.
Line 45:		Line 49:
	$ '''sudo rm -r /var/www/jinzora2/install'''		$ '''sudo rm -r /var/www/jinzora2/install'''

-	=== ~~Links~~ ===	+	== Create an Apache HTTPS instance ==
-		+
-	* [http://www.linode.com/wiki/index.php/Apache2_SSL_in_Ubuntu Apache2 SSL in Ubuntu]	+
-	* [http://www.netadmintools.com/art90.html Changing the root password on MySQL]	+
-	* [http://lifehacker.com/software/home-server/geek-to-live-build-an-internet-jukebox-with-jinzora-254178.php Geek to Live: Build an internet jukebox with Jinzora]	+
-	* [http://www.howtoforge.com/ultimate_freebsd_media_server The Ultimate Media Server - Apache+SSL , PHP, MySQL and Jinzora]	+

	* Create a private key for the Apache server.		* Create a private key for the Apache server.
Line 104:		Line 103:
	* Reload Apache for the changes to take effect.		* Reload Apache for the changes to take effect.
	$ '''sudo /etc/init.d/apache2 reload'''		$ '''sudo /etc/init.d/apache2 reload'''
		+
		+	=== Links ===
		+
		+	* [http://www.linode.com/wiki/index.php/Apache2_SSL_in_Ubuntu Apache2 SSL in Ubuntu]
		+	* [http://www.netadmintools.com/art90.html Changing the root password on MySQL]
		+	* [http://lifehacker.com/software/home-server/geek-to-live-build-an-internet-jukebox-with-jinzora-254178.php Geek to Live: Build an internet jukebox with Jinzora]
		+	* [http://www.howtoforge.com/ultimate_freebsd_media_server The Ultimate Media Server - Apache+SSL , PHP, MySQL and Jinzora]

Hutch at 20:03, 4 October 2007

Hutch — Thu, 04 Oct 2007 20:03:13 GMT

←Older revision		Revision as of 20:03, 4 October 2007
Line 64:		Line 64:

	* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.		* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.
-	$ '''openssl rsa -in server.key -out server.key'''	+	$ '''openssl rsa -in server.key -out server.pem'''
		+	$ '''rm server.key'''

	* Move the Apache certificate and private key to the Apache directory and configure permissions.		* Move the Apache certificate and private key to the Apache directory and configure permissions.
-	$ '''sudo mv server.~~key~~ /etc/apache2/apache.pem'''	+	$ '''sudo mv server.pem /etc/apache2/apache.pem'''
	$ '''sudo mv server.crt /etc/apache2/apache.crt'''		$ '''sudo mv server.crt /etc/apache2/apache.crt'''
	$ '''sudo chown root:root /etc/apache2/apache.pem'''		$ '''sudo chown root:root /etc/apache2/apache.pem'''

Hutch at 19:56, 4 October 2007

Hutch — Thu, 04 Oct 2007 19:56:49 GMT

←Older revision		Revision as of 19:56, 4 October 2007
Line 75:		Line 75:
	$ '''sudo a2enmod ssl'''		$ '''sudo a2enmod ssl'''

-	* Configure Apache to listen on port 443 (~~https~~).	+	* Configure Apache to listen on port 443 (HTTPS).
	$ '''sudo sh -c 'echo "Listen 443" >> /etc/apache2/ports.conf''''		$ '''sudo sh -c 'echo "Listen 443" >> /etc/apache2/ports.conf''''

-	* Create an ~~https~~ site.	+	* Create an HTTPS site.
	$ '''sudo cp /etc/apache2/sites-available/default /etc/apache2/sites-available/ssl'''		$ '''sudo cp /etc/apache2/sites-available/default /etc/apache2/sites-available/ssl'''

-	* Modify ''/etc/apache2/sites-available/ssl'':	+	* Modify ''/etc/apache2/sites-available/ssl''.
	Before:		Before:

Line 97:		Line 97:
	'''SSLCertificateFile /etc/apache2/apache.crt'''		'''SSLCertificateFile /etc/apache2/apache.crt'''
	'''SSLCertificateKeyFile /etc/apache2/apache.pem'''		'''SSLCertificateKeyFile /etc/apache2/apache.pem'''
		+
		+	* Enable the HTTPS site.
		+	$ '''sudo a2ensite ssl'''
		+
		+	* Reload Apache for the changes to take effect.
		+	$ '''sudo /etc/init.d/apache2 reload'''

Hutch at 19:51, 4 October 2007

Hutch — Thu, 04 Oct 2007 19:51:28 GMT

←Older revision		Revision as of 19:51, 4 October 2007
Line 66:		Line 66:
	$ '''openssl rsa -in server.key -out server.key'''		$ '''openssl rsa -in server.key -out server.key'''

		+	* Move the Apache certificate and private key to the Apache directory and configure permissions.
		+	$ '''sudo mv server.key /etc/apache2/apache.pem'''
		+	$ '''sudo mv server.crt /etc/apache2/apache.crt'''
		+	$ '''sudo chown root:root /etc/apache2/apache.pem'''
		+	$ '''sudo chmod 400 /etc/apache2/apache.pem'''

-	$ sudo ~~mv server~~.~~key server~~.~~crt~~ /~~usr~~/~~lib~~/apache2/	+	* Enable mod_ssl within Apache.
		+	$ '''sudo a2enmod ssl'''
		+
		+	* Configure Apache to listen on port 443 (https).
		+	$ '''sudo sh -c 'echo "Listen 443" >> /etc/apache2/ports.conf''''
		+
		+	* Create an https site.
		+	$ '''sudo cp /etc/apache2/sites-available/default /etc/apache2/sites-available/ssl'''
		+
		+	* Modify ''/etc/apache2/sites-available/ssl'':
		+	Before:
		+
		+	NameVirtualHost *
		+	<VirtualHost *>
		+	ServerAdmin webmaster@localhost
		+
		+	After:
		+
		+	NameVirtualHost *''':443'''
		+	<VirtualHost *''':443'''>
		+	ServerAdmin webmaster@localhost
		+
		+	'''SSLEngine On'''
		+	'''SSLCertificateFile /etc/apache2/apache.crt'''
		+	'''SSLCertificateKeyFile /etc/apache2/apache.pem'''

Hutch at 19:38, 4 October 2007

Hutch — Thu, 04 Oct 2007 19:38:51 GMT

←Older revision		Revision as of 19:38, 4 October 2007
Line 61:		Line 61:
	$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''		$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''

-	* If you receive a '''unable to write 'random state'''' error, change permissions on ''~/.rnd'' so that it is writable by the user running the command.	+	If you receive an '''unable to write 'random state'''' error, change permissions on ''~/.rnd'' so that it is writable by the user running the command.

	* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.		* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.

Hutch at 19:37, 4 October 2007

Hutch — Thu, 04 Oct 2007 19:37:53 GMT

←Older revision		Revision as of 19:37, 4 October 2007
Line 60:		Line 60:
	* Create a self-signed server certificate by using the private key to sign the CSR.		* Create a self-signed server certificate by using the private key to sign the CSR.
	$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''		$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''
		+
		+	* If you receive a '''unable to write 'random state'''' error, change permissions on ''~/.rnd'' so that it is writable by the user running the command.

	* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.		* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.

Hutch at 19:27, 4 October 2007

Hutch — Thu, 04 Oct 2007 19:27:00 GMT

←Older revision		Revision as of 19:27, 4 October 2007
Line 61:		Line 61:
	$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''		$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''

-		+	* Remove the private key passphrase (i.e., create an unencrypted PEM version of the private key) so that Apache can start without user interaction.
		+	$ '''openssl rsa -in server.key -out server.key'''

-	WIP
-
-	$ openssl x509 -req -days 3650 -in server.csr -signkey server.key -out server.crt
-	Signature ok
-	subject=/C=US/ST=Minnesota/L=Minneapolis/O=Navitaire Ltd./CN=hutch.navitaire.com
-	Getting Private key
-	Enter pass phrase for server.key:
-	unable to write 'random state'
-	hutch@hutch:~$ ls -ld ~/.rnd
-	-rw------- 1 root root 1024 2007-08-20 17:17 /home/hutch/.rnd
-	$ sudo chown hutch:hutch ~/.rnd
-	$ openssl x509 -req -days 3650 -in server.csr -signkey server.key -out server.crt
-	Signature ok
-	subject=/C=US/ST=Minnesota/L=Minneapolis/O=Navitaire Ltd./CN=hutch.navitaire.com
-	Getting Private key
-	Enter pass phrase for server.key:
-	$

	$ sudo mv server.key server.crt /usr/lib/apache2/		$ sudo mv server.key server.crt /usr/lib/apache2/

Hutch at 19:14, 4 October 2007

Hutch — Thu, 04 Oct 2007 19:14:36 GMT

←Older revision		Revision as of 19:14, 4 October 2007
Line 56:		Line 56:

	* Create a Certificate Signing Request (CSR). Make sure the Common Name is equal to fully-qualified domain name of your Web server (i.e., if you will access your Web server at https://host.example.com, the Common Name should be host.example.com).		* Create a Certificate Signing Request (CSR). Make sure the Common Name is equal to fully-qualified domain name of your Web server (i.e., if you will access your Web server at https://host.example.com, the Common Name should be host.example.com).
-	$ openssl req -new -key server.key -out server.csr	+	$ '''openssl req -new -key server.key -out server.csr'''

	* Create a self-signed server certificate by using the private key to sign the CSR.		* Create a self-signed server certificate by using the private key to sign the CSR.
-		+	$ '''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt'''