<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ball Dawg! &#187; https</title>
	<atom:link href="http://www.balldawg.net/index.php/tag/https/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.balldawg.net</link>
	<description>Just some ninja monkeys, nothing to see here.  Move along.</description>
	<lastBuildDate>Fri, 13 Jan 2012 02:02:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Setting up SSL on Remote Lights Out Cards</title>
		<link>http://www.balldawg.net/index.php/2009/05/setting-up-ssl-on-remote-lights-out-cards/</link>
		<comments>http://www.balldawg.net/index.php/2009/05/setting-up-ssl-on-remote-lights-out-cards/#comments</comments>
		<pubDate>Tue, 19 May 2009 22:07:21 +0000</pubDate>
		<dc:creator>Andrew Rankin</dc:creator>
				<category><![CDATA[Remote Lights Out]]></category>
		<category><![CDATA[Server Management]]></category>
		<category><![CDATA[Bladecenter]]></category>
		<category><![CDATA[CA]]></category>
		<category><![CDATA[Certificate Authority]]></category>
		<category><![CDATA[Dell]]></category>
		<category><![CDATA[Drac]]></category>
		<category><![CDATA[elom]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[IBM]]></category>
		<category><![CDATA[iLo]]></category>
		<category><![CDATA[RSA II]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[Sun]]></category>

		<guid isPermaLink="false">http://www.balldawg.net/?p=123</guid>
		<description><![CDATA[In an attempt to up security and stop sending our passwords over clear text, I recently setup an in house certificate authority at work. While I&#8217;m not going to go through setting up the actual CA (see g-loaded.eu), I am going to go through the steps of how to set up a few different hardware [...]]]></description>
			<content:encoded><![CDATA[<p>In an attempt to up security and stop sending our passwords over clear text, I recently setup an in house certificate authority at work.   While I&#8217;m not going to go through setting up the actual CA (see <a href="http://www.g-loaded.eu/2005/11/10/be-your-own-ca/" target="_blank">g-loaded.eu</a>), I am going to go through the steps of how to set up a few different hardware vendor/types to work with a signed certificate.  One thing I learned during this process is that almost every single product, even made by the same company, is different.<br />
<span id="more-123"></span></p>
<p><strong>IBM BladeCenters</strong></p>
<p>&gt; Get the key from the BladeCenter</p>
<ol>
<li> Login to the BladeCenter</li>
<li>Expand &#8220;MM Control&#8221;</li>
<li>Click &#8220;Network Protocols&#8221;</li>
<li>Click &#8220;Secure Shell (SSH) Server&#8221;</li>
<li>Under the SSL for &#8220;Web Server click Generate&#8221; a &#8220;Generate a New Server Key and Certificate Signing Request (CSR)&#8221;</li>
<li>You&#8217;ll need to fill out the requested information down to SurName, then click &#8220;Generate CSR&#8221;</li>
<li>Save the key to your machine, prepend machine. (bladecenter.) to the beginning of the file name to denote where it came from</li>
</ol>
<p>&gt; SCP the file to root@server:/path/to/your/CA/requests/<br />
&gt; To convert the DER encoded CSR to a PEM encoded CSR, within the above folder, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA/requests
openssl req -inform DER -in bladecenter.csr_server.der -out bladecenter.csr.pem -outform PEM
</pre>
<p>&gt; To sign the key, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA
openssl ca -config openssl.cnf -policy policy_anything -out certs/bladecenter.crt -infiles requests/bladecenter.csr.pem
</pre>
<p>&gt; Convert the created .crt file to a .der file, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA/certs
openssl x509 -in bladecenter.crt -inform PEM -out bladecenter.crt.der -outform DER
</pre>
<p>&gt; SCP the cert file (/path/to/your/CA/certs/bladecenter.crt.der) back to your system<br />
&gt; Import the cert into the AMM</p>
<ol>
<li>Click &#8220;Import a Signed Certificate to the Server&#8221;</li>
<li>Browse for the file you just copied back from server (bladecenter.crt.der)</li>
<li>Click &#8220;Import Server Certificate&#8221;</li>
</ol>
<p><strong>IBM RSA II</strong></p>
<p>&gt; Get the key from the RSA II Controller</p>
<ol>
<li>Login to the RSA II Controller</li>
<li>Click &#8220;Security&#8221;</li>
<li>Under the SSL for &#8220;Web Server click Generate&#8221; a &#8220;Generate a New Server Key and Certificate Signing Request (CSR)&#8221;</li>
<li>You&#8217;ll need to fill out the requested information down to SurName, then click &#8220;Generate CSR&#8221;</li>
</ol>
<p>&gt; Save the key to your machine, prepend machine. (rsa.) to the beginning of the file name to denote where it came from<br />
&gt; SCP the file to root@server:/path/to/your/CA/requests/<br />
&gt; To convert the DER encoded CSR to a PEM encoded CSR, within the above folder, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA/requests
openssl req -inform DER -in rsa.csr_server.der -out rsa.csr.pem -outform PEM
</pre>
<p>&gt; To sign the key, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA
openssl ca -config openssl.cnf -policy policy_anything -out certs/rsa.crt -infiles requests/rsa.csr.pem
</pre>
<p>&gt; Convert the created .crt file to a .der file, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA/certs
openssl x509 -in rsa.crt -inform PEM -out rsa.crt.der -outform DER
</pre>
<p>&gt; SCP the cert file (/path/to/your/CA/rsa.crt.der) back to your system<br />
&gt; Import the cert into the RSA II Controller</p>
<ol>
<li> Click &#8220;Import a Signed Certificate to the Server&#8221;</li>
<li>Browse for the file you just copied back from server (rsa.crt.der)</li>
<li>Click &#8220;Import Server Certificate&#8221;</li>
</ol>
<p><strong>HP iLO</strong></p>
<p>&gt; Get the Signing Request from the iLO</p>
<ol>
<li>Login to the iLO</li>
<li>Hover over &#8220;Administration&#8221;</li>
<li>Select &#8220;Certificate Administration&#8221;</li>
<li>Click &#8220;Create Certificate Request&#8221;</li>
<li>Copy and paste the request from the box and into server:/path/to/your/CA/requests/ilo.csr.pem</li>
</ol>
<p>&gt; To sign the key, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA
openssl ca -config openssl.cnf -policy policy_anything -out certs/ilo.crt -infiles requests/ilo.csr.pem
</pre>
<p>&gt; Import the cert into the iLO</p>
<ol>
<li>Click &#8220;Import Certificate&#8221;</li>
<li>Enter the contents of /path/to/your/CA/certs/ilo.crt into the provided box</li>
<li>Click &#8220;Next&#8221;</li>
</ol>
<p><strong>Sun eLOM</strong></p>
<p>&gt; Get the Signing Request from the eLOM</p>
<ol>
<li> Login to the eLOM</li>
<li>Click &#8220;Configuration&#8221;</li>
<li>Click &#8220;System Management Access&#8221;</li>
<li>Click &#8220;SSL Certificate&#8221;</li>
<li>Select &#8220;Certificate&#8221; and click &#8220;Select&#8221;</li>
</ol>
<p>&gt; Generate the request:</p>
<pre class="brush: sh">
cd /path/to/your/CA
openssl req -config openssl.cnf -new -nodes -keyout private/elom.key -out requests/elom.csr -days 365
</pre>
<p><strong>You&#8217;ll be asked specific questions about the servers location, most of the defaults have been set in openssl.cnf, however you&#8217;ll need to make sure the domain name (CN) is correct.</strong></p>
<p>&gt; Sign the key:</p>
<pre class="brush: sh">
cd /path/to/your/CA
openssl ca -config openssl.cnf -policy policy_anything -out certs/elom.crt -infiles requests/elom.csr
</pre>
<p>&gt; Import the Key on the eLOM</p>
<ol>
<li> Upload the generated Certificate first (server:/path/to/your/CA/certs/elom.crt)</li>
<li>Upload the generated Key Second (server:/path/to/your/CA/private/elom.key)</li>
</ol>
<p><strong>Dell DRAC</strong></p>
<p>&gt; Get the Signing Request from the DRAC</p>
<ol>
<li> Login to the DRAC</li>
<li>Click the &#8220;Configuration&#8221; tab</li>
<li>Click the &#8220;Security&#8221; tab</li>
<li>Select &#8220;Generate a new Certificate Signing Request (CSR)&#8221;</li>
<li>Click &#8220;Next&#8221;</li>
<li>Complete the listed fields making sure that the &#8220;Common Name&#8221; (CN) is the full host name of the console</li>
<li>Click &#8220;Generate&#8221;, wait for it to generate the request.  It will pop up with a download for &#8220;csr.txt&#8221; when it is complete.  Save the file.</li>
<li>Rename csr.txt to include the hostname of the box, EX: drac.csr.txt</li>
<li>SCP the file to root@server:/path/to/your/CA/requests</li>
</ol>
<p>&gt; To sign the key, run:</p>
<pre class="brush: sh">
cd /path/to/your/CA
openssl ca -config openssl.cnf -policy policy_anything -out certs/drac.crt -infiles requests/drac.csr.txt
</pre>
<p>&gt; Edit the crt file to remove everything above the &#8220;&#8212;&#8211;BEGIN CERTIFICATE&#8212;&#8211;&#8221; line<br />
<strong> &gt; Save the File with DOS-style Line-Ending CR-LF (:set ff=dos in vi)</strong><br />
&gt; Import the cert into the DRAC</p>
<ol>
<li> Return to &#8220;Certificate Management&#8221;</li>
<li>Select &#8220;Upload DRAC 4 server certificate&#8221;</li>
<li>Click &#8220;Next&#8221;</li>
<li>Select the certificate you just signed</li>
<li>Click &#8220;Upload&#8221;</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.balldawg.net/index.php/2009/05/setting-up-ssl-on-remote-lights-out-cards/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

