<?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 for DigiCert</title>
	<atom:link href="/comments/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>SSL Digital Certificate Authority - Encryption &#38; Authentication</description>
	<lastBuildDate>Mon, 20 Feb 2017 00:52:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on Browser Security Icon Updates and SHA-1 Deprecation by Charles Grayson Jr</title>
		<link>/blog/browser-security-icon-updates-sha-1-deprecation/#comment-193</link>
		<dc:creator><![CDATA[Charles Grayson Jr]]></dc:creator>
		<pubDate>Mon, 20 Feb 2017 00:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=5787#comment-193</guid>
		<description><![CDATA[Since I upgraded to Mozilla Firefox 51, any Yahoo mail page with images gives the yellow warning on the grayed out lock.  Clicking on the icon gives me DigiCert message saying that I don&#039;t have a secure connection.  How can i secure the link.   This includes emails from Amazon among others.
This is not an issue on Mozilla 50.

Thanks for any suggestions]]></description>
		<content:encoded><![CDATA[<p>Since I upgraded to Mozilla Firefox 51, any Yahoo mail page with images gives the yellow warning on the grayed out lock.  Clicking on the icon gives me DigiCert message saying that I don&#8217;t have a secure connection.  How can i secure the link.   This includes emails from Amazon among others.<br />
This is not an issue on Mozilla 50.</p>
<p>Thanks for any suggestions</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should I Buy from This Site? How to Know if a Website is Secure by Shalandria Dean</title>
		<link>/blog/how-to-know-if-a-website-is-secure/#comment-76</link>
		<dc:creator><![CDATA[Shalandria Dean]]></dc:creator>
		<pubDate>Sat, 18 Feb 2017 19:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=1962#comment-76</guid>
		<description><![CDATA[What steps I need to take]]></description>
		<content:encoded><![CDATA[<p>What steps I need to take</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Phishing: A Trending Threat for 2015 by Mary Catherine</title>
		<link>/blog/phishing-trending-threat-for-2015/#comment-182</link>
		<dc:creator><![CDATA[Mary Catherine]]></dc:creator>
		<pubDate>Mon, 13 Feb 2017 03:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=4435&#038;preview_id=4435#comment-182</guid>
		<description><![CDATA[Also I know it is digicert that have the certificate. I also know the algorithm pattern, serial number and location. This is illegal]]></description>
		<content:encoded><![CDATA[<p>Also I know it is digicert that have the certificate. I also know the algorithm pattern, serial number and location. This is illegal</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Phishing: A Trending Threat for 2015 by Mary Catherine</title>
		<link>/blog/phishing-trending-threat-for-2015/#comment-181</link>
		<dc:creator><![CDATA[Mary Catherine]]></dc:creator>
		<pubDate>Mon, 13 Feb 2017 03:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=4435&#038;preview_id=4435#comment-181</guid>
		<description><![CDATA[What are other ways someone could be operating my mac and use my keychain as if admin? Its unlikely an email is to blame.]]></description>
		<content:encoded><![CDATA[<p>What are other ways someone could be operating my mac and use my keychain as if admin? Its unlikely an email is to blame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Where Is Your Private Key? by Raúl Maguiña Huerta</title>
		<link>/blog/where-is-your-private-key/#comment-137</link>
		<dc:creator><![CDATA[Raúl Maguiña Huerta]]></dc:creator>
		<pubDate>Sun, 18 Dec 2016 07:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=3539&#038;preview_id=3539#comment-137</guid>
		<description><![CDATA[Hi. I&#039;m having the same problem, but I do know where my private key is (on the same file as the certificate). Digicert for windows isn&#039;t able to retrieve it. I keep on getting the same answer &quot;The private key for this certificate could not be found in the machine or current key stores&quot;. What should I do? please help.]]></description>
		<content:encoded><![CDATA[<p>Hi. I&#8217;m having the same problem, but I do know where my private key is (on the same file as the certificate). Digicert for windows isn&#8217;t able to retrieve it. I keep on getting the same answer &#8220;The private key for this certificate could not be found in the machine or current key stores&#8221;. What should I do? please help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fix for an Expired Intermediate SSL Certificate Chain by Expired certificates cost businesses $15 million per outage &#124; CSO Online</title>
		<link>/blog/expired-intermediate-certificate/#comment-43</link>
		<dc:creator><![CDATA[Expired certificates cost businesses $15 million per outage &#124; CSO Online]]></dc:creator>
		<pubDate>Fri, 09 Dec 2016 20:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=855#comment-43</guid>
		<description><![CDATA[[&#8230;] Also this past spring, smart home company Wink Inc., had to recall its $50 Wink Hubs because of an expired certificate. [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] Also this past spring, smart home company Wink Inc., had to recall its $50 Wink Hubs because of an expired certificate. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 45% of Healthcare Breaches Occur on Stolen Laptops by Stolen Patient Medical Records are a Massive Healthcare Security Risk. Here’s How to Prevent It. &#124; Inside BlackBerry</title>
		<link>/blog/45-percent-healthcare-breaches-occur-on-laptops/#comment-190</link>
		<dc:creator><![CDATA[Stolen Patient Medical Records are a Massive Healthcare Security Risk. Here’s How to Prevent It. &#124; Inside BlackBerry]]></dc:creator>
		<pubDate>Fri, 09 Dec 2016 13:49:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=4942&#038;preview_id=4942#comment-190</guid>
		<description><![CDATA[[&#8230;] That scenario is much more common than you might think, but it’s far from the only way protected health information (PHI) might be compromised by criminals.  PHI is some of the most valuable data on the market for criminals. That means that if you aren’t taking the necessary precautions to protect your patients, their private details will eventually end up in the wrong hands. [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] That scenario is much more common than you might think, but it’s far from the only way protected health information (PHI) might be compromised by criminals.  PHI is some of the most valuable data on the market for criminals. That means that if you aren’t taking the necessary precautions to protect your patients, their private details will eventually end up in the wrong hands. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Replace Your Certificates for Internal Names: Part 2 by Homepage</title>
		<link>/blog/replace-internal-names-certificates-part-2/#comment-160</link>
		<dc:creator><![CDATA[Homepage]]></dc:creator>
		<pubDate>Thu, 13 Oct 2016 10:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=3684&#038;preview_id=3684#comment-160</guid>
		<description><![CDATA[&lt;strong&gt;... [Trackback]&lt;/strong&gt;

[...] Informations on that Topic: blog.digicert.com/replace-internal-names-certificates-part-2/ [...]]]></description>
		<content:encoded><![CDATA[<p><strong>&#8230; [Trackback]</strong></p>
<p>[&#8230;] Informations on that Topic: blog.digicert.com/replace-internal-names-certificates-part-2/ [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Ending Trust for SHA-1 SSL Sites, How it Affects You by Homepage</title>
		<link>/blog/ending-trust-sha-1/#comment-57</link>
		<dc:creator><![CDATA[Homepage]]></dc:creator>
		<pubDate>Sat, 10 Sep 2016 03:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digicert.com/?p=1352#comment-57</guid>
		<description><![CDATA[&lt;strong&gt;... [Trackback]&lt;/strong&gt;

[...] Read More: blog.digicert.com/ending-trust-sha-1/ [...]]]></description>
		<content:encoded><![CDATA[<p><strong>&#8230; [Trackback]</strong></p>
<p>[&#8230;] Read More: blog.digicert.com/ending-trust-sha-1/ [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
