<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SSL problem</title>
	<atom:link href="http://morgajel.net/2006/06/19/132/feed/" rel="self" type="application/rss+xml" />
	<link>http://morgajel.net/2006/06/19/132/</link>
	<description>Stemming the flow of evincible Ignorance. We must try to understand for the sake of understanding.</description>
	<pubDate>Mon, 08 Sep 2008 18:14:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Stone</title>
		<link>http://morgajel.net/2006/06/19/132/#comment-1104</link>
		<dc:creator>Stone</dc:creator>
		<pubDate>Thu, 22 Jun 2006 02:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://morgajel.net/2006/06/19/132/#comment-1104</guid>
		<description>How about GoDaddy https://www.godaddy.com/gdshop/ssl/ssl.asp?se=%2B&#38;ci=271

You can get certs starting out at $20 a year and 256 bit encryption.  I think those ones won't give you trouble but I am not 100% sure.  At that price you could easily add that into the service charge for email so it doesn't come out of your bottom line.

The other thing is you could do a self signed cert.  The downside is that the client would have to install the cert everytime they were on a new computer, such as internet cafe or public kiosk.  But it is free and you can generate keys for each domain.

If they are running a Windows AD environment you can set up a certificate authority in the domain and issue their own domain certs applied through GPOs.  Then you can issue one cert from their AD domain and use it for their mail domain.  This would get rid of the need for their corporate workstations to manually install the cert since it would be applied to the domain, but public machines would will need to install the cert when they needed to use it.

In Windows go to Start &#62; Programs &#62; Administrative Tools &#62; Public Key Management.  Then select Certificates &#62; Trusted Root Certification Authority &#62; Certificates to see what certs are automagically trusted by Windows, then you can search for a cheap one.</description>
		<content:encoded><![CDATA[<p>How about GoDaddy <a href="https://www.godaddy.com/gdshop/ssl/ssl.asp?se=%2B&amp;ci=271" rel="nofollow">https://www.godaddy.com/gdshop/ssl/ssl.asp?se=%2B&amp;ci=271</a></p>
<p>You can get certs starting out at $20 a year and 256 bit encryption.  I think those ones won&#8217;t give you trouble but I am not 100% sure.  At that price you could easily add that into the service charge for email so it doesn&#8217;t come out of your bottom line.</p>
<p>The other thing is you could do a self signed cert.  The downside is that the client would have to install the cert everytime they were on a new computer, such as internet cafe or public kiosk.  But it is free and you can generate keys for each domain.</p>
<p>If they are running a Windows AD environment you can set up a certificate authority in the domain and issue their own domain certs applied through GPOs.  Then you can issue one cert from their AD domain and use it for their mail domain.  This would get rid of the need for their corporate workstations to manually install the cert since it would be applied to the domain, but public machines would will need to install the cert when they needed to use it.</p>
<p>In Windows go to Start &gt; Programs &gt; Administrative Tools &gt; Public Key Management.  Then select Certificates &gt; Trusted Root Certification Authority &gt; Certificates to see what certs are automagically trusted by Windows, then you can search for a cheap one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
