<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google Checkout - Confusing Security Information</title>
	<atom:link href="http://www.brainhandles.com/techno-thoughts/google-checkout-confusing-security-information/feed" rel="self" type="application/rss+xml" />
	<link>http://www.brainhandles.com/techno-thoughts/google-checkout-confusing-security-information</link>
	<description>Whatever&#039;s tugging at my brain handles</description>
	<lastBuildDate>Tue, 27 Dec 2011 19:46:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ruben Calvey</title>
		<link>http://www.brainhandles.com/techno-thoughts/google-checkout-confusing-security-information/comment-page-1#comment-16519</link>
		<dc:creator>Ruben Calvey</dc:creator>
		<pubDate>Fri, 10 Jun 2011 00:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.brainhandles.com/2007/02/10/google-checkout-confusing-security-information/#comment-16519</guid>
		<description>Nice post. I finally took the plunge and bought an ssl certificate for my site, although I had no idea how confusing it would be to configure. I eventually got things straightened out, but I can&#039;t help thinking there must be a more straightforward way to secure a web site. I dread the switch to IPV6!</description>
		<content:encoded><![CDATA[<p>Nice post. I finally took the plunge and bought an ssl certificate for my site, although I had no idea how confusing it would be to configure. I eventually got things straightened out, but I can't help thinking there must be a more straightforward way to secure a web site. I dread the switch to IPV6!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Fox</title>
		<link>http://www.brainhandles.com/techno-thoughts/google-checkout-confusing-security-information/comment-page-1#comment-11347</link>
		<dc:creator>Ryan Fox</dc:creator>
		<pubDate>Wed, 08 Sep 2010 19:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.brainhandles.com/2007/02/10/google-checkout-confusing-security-information/#comment-11347</guid>
		<description>The Google List is a list of the common names of certificates in their trust store.  They may or may not match any branding the CA markets their certificate signing service under.  They will, however, match the common name of the CA&#039;s root certificate.

All certificates signed by Go Daddy are signed by root certificates given in that list.</description>
		<content:encoded><![CDATA[<p>The Google List is a list of the common names of certificates in their trust store.  They may or may not match any branding the CA markets their certificate signing service under.  They will, however, match the common name of the CA's root certificate.</p>
<p>All certificates signed by Go Daddy are signed by root certificates given in that list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.brainhandles.com/techno-thoughts/google-checkout-confusing-security-information/comment-page-1#comment-10166</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Sat, 22 May 2010 08:08:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.brainhandles.com/2007/02/10/google-checkout-confusing-security-information/#comment-10166</guid>
		<description>Wow, over 3 years since your post and this is still a confusing issue.  I just left the following post in the Google Checkout integration forum on this exact topic.

I need to buy an SSL cert for the API URL callback for Google Checkout.  Go Daddy has great prices for certs that are in 99% of browsers.  Google states that the &quot;Go Daddy Class 2 CA&quot; certificate is supported.  However, all certs issued by Go Daddy seem to have an issuer of &quot;Go Daddy Secure Certification Authority&quot;.  I&#039;ve checked several websites they&#039;ve issued SSL certs to, and none of those certs have an issuer of &quot;Go Daddy Class 2 CA&quot;.  Is the &quot;Go Daddy Class 2 CA&quot; just a generic, marketing reference to the certs issued by &quot;Go Daddy Secure Certification Authority&quot;?  As of this posting, I see two certs that Go Daddy sells.  They are &quot;Standard SSL&quot; and &quot;Premium SSL&quot;, but no details on the actual issuer.  Will either of those certs work for the API URL callback?

I used the Digicert tool to verify the various Go Daddy SSL certs I found.

http://checkout.google.com/support/sell/bin/answer.py?answer=57856
http://www.godaddy.com/ssl/ssl-certificates.aspx?isc=sslqgo015b&amp;ci=8979
https://www.digicert.com/help/

The post url:
http://www.google.com/support/forum/p/checkout-merchants/thread?tid=770925055e03e08b&amp;hl=en</description>
		<content:encoded><![CDATA[<p>Wow, over 3 years since your post and this is still a confusing issue.  I just left the following post in the Google Checkout integration forum on this exact topic.</p>
<p>I need to buy an SSL cert for the API URL callback for Google Checkout.  Go Daddy has great prices for certs that are in 99% of browsers.  Google states that the "Go Daddy Class 2 CA" certificate is supported.  However, all certs issued by Go Daddy seem to have an issuer of "Go Daddy Secure Certification Authority".  I've checked several websites they've issued SSL certs to, and none of those certs have an issuer of "Go Daddy Class 2 CA".  Is the "Go Daddy Class 2 CA" just a generic, marketing reference to the certs issued by "Go Daddy Secure Certification Authority"?  As of this posting, I see two certs that Go Daddy sells.  They are "Standard SSL" and "Premium SSL", but no details on the actual issuer.  Will either of those certs work for the API URL callback?</p>
<p>I used the Digicert tool to verify the various Go Daddy SSL certs I found.</p>
<p><a href="http://checkout.google.com/support/sell/bin/answer.py?answer=57856" rel="nofollow">http://checkout.google.com/support/sell/bin/answer.py?answer=57856</a><br />
<a href="http://www.godaddy.com/ssl/ssl-certificates.aspx?isc=sslqgo015b&#038;ci=8979" rel="nofollow">http://www.godaddy.com/ssl/ssl-certificates.aspx?isc=sslqgo015b&#038;ci=8979</a><br />
<a href="https://www.digicert.com/help/" rel="nofollow">https://www.digicert.com/help/</a></p>
<p>The post url:<br />
<a href="http://www.google.com/support/forum/p/checkout-merchants/thread?tid=770925055e03e08b&#038;hl=en" rel="nofollow">http://www.google.com/support/forum/p/checkout-merchants/thread?tid=770925055e03e08b&#038;hl=en</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy</title>
		<link>http://www.brainhandles.com/techno-thoughts/google-checkout-confusing-security-information/comment-page-1#comment-9986</link>
		<dc:creator>Tommy</dc:creator>
		<pubDate>Mon, 29 Mar 2010 00:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.brainhandles.com/2007/02/10/google-checkout-confusing-security-information/#comment-9986</guid>
		<description>I am using google checkout and am in the middle of some serious changes t my shopping cart. I added google checkout as a new payment option and needed to install the moduale, create new tables in my database, purchase ssl all this just to have google checkout as a payment option for people in my shop! I also use paypal but needing to purchase an ssl just to use google checkout with there transaction service is what get me! All i can say is it&#039;s a pain in the butt but i think in the end I&#039;ll be happy i bought the ssl and have both paypal and google checkout!</description>
		<content:encoded><![CDATA[<p>I am using google checkout and am in the middle of some serious changes t my shopping cart. I added google checkout as a new payment option and needed to install the moduale, create new tables in my database, purchase ssl all this just to have google checkout as a payment option for people in my shop! I also use paypal but needing to purchase an ssl just to use google checkout with there transaction service is what get me! All i can say is it's a pain in the butt but i think in the end I'll be happy i bought the ssl and have both paypal and google checkout!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

