<?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>Sean&#039;s Blog &#187; https</title>
	<atom:link href="http://seanbehan.com/tag/https/feed/" rel="self" type="application/rss+xml" />
	<link>http://seanbehan.com</link>
	<description>Web Programming, Ruby on Rails, Wordpress, PHP from Burlington, Vermont</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:44:54 +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>OpenSSL Certificate Generation Information for Certificate Authority to Serve Traffic Over Https</title>
		<link>http://seanbehan.com/linux/openssl-certificate-generation-information-for-certificate-authority-to-serve-traffic-over-https/</link>
		<comments>http://seanbehan.com/linux/openssl-certificate-generation-information-for-certificate-authority-to-serve-traffic-over-https/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 21:43:26 +0000</pubDate>
		<dc:creator>bseanvt</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[common name]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://seanbehan.com/?p=483</guid>
		<description><![CDATA[apt-get install openssl openssl genrsa -des3 -out server.key 1024 openssl req -new -key server.key -out server.csr You&#8217;ll be prompted to enter a password (don&#8217;t forget it!) as well as fill in company identity information. The most important part is the common name, which is actually the domain you are requesting the certificate for. If you&#8217;re [...]]]></description>
			<content:encoded><![CDATA[<div style="height:33px;" class="really_simple_share robots-nocontent snap_nopreview"><div class="really_simple_share_facebook_like" style="width:px;">
				<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fseanbehan.com%2Flinux%2Fopenssl-certificate-generation-information-for-certificate-authority-to-serve-traffic-over-https%2F&amp;layout=button_count&amp;show_faces=false&amp;width=&amp;action=like&amp;colorscheme=light&amp;send=false&amp;height=27" 
						scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:px; height:27px;" allowTransparency="true"></iframe>
				</div><div class="really_simple_share_twitter" style="width:px;">
					<a href="http://twitter.com/share" class="twitter-share-button" data-count="horizontal" 
						data-text="OpenSSL Certificate Generation Information for Certificate Authority to Serve Traffic Over Https" data-url="http://seanbehan.com/linux/openssl-certificate-generation-information-for-certificate-authority-to-serve-traffic-over-https/" 
						data-via="" ></a> 
				</div></div>
		<div style="clear:both;"></div><pre class="wp-code-highlight prettyprint">
apt-get install openssl
openssl genrsa -des3 -out server.key 1024
openssl req -new -key server.key -out server.csr
</pre>
<p>You&#8217;ll be prompted to enter a password (don&#8217;t forget it!) as well as fill in company identity information. The most important part is the common name, which is actually the domain you are requesting the certificate for. If you&#8217;re going without a wildcard certificate you can specify the subdomain ( secure.seanbehan.com ) otherwise it assumes www.seanbehan.com and seanbehan.com to be the same, and will cover both domains www.seanbehan.com and  seanbehan.com&#8230; however, it will not cover anything.seanbehan.com. Unless you get a wildcard certificate (these cost more money). Enter company details such as country code, state and the rest are pretty self explanatory.</p>
<p>You need to then submit the server.csr file contents to a certificate authority like godaddy, verisign, etc.<br />
Grab the contents by opening up the file</p>
<pre class="wp-code-highlight prettyprint"> vim server.csr </pre>
<p>After you submit it to them, they then will confirm that everything is correct and then give you the signed certificate back for your use on your server. Unless of course you&#8217;re faking your company details and are an evil, wicked spammer!</p>
<p>The certificate authority (CA) should give you instructions for installing the cert, as well as other files so that you can serve secure pages w/out any browser troubles!</p>
]]></content:encoded>
			<wfw:commentRss>http://seanbehan.com/linux/openssl-certificate-generation-information-for-certificate-authority-to-serve-traffic-over-https/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

