<?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: Gmail now HTTPS by default</title>
	<atom:link href="http://securitymusings.com/article/1642/gmail-now-https-by-default/feed" rel="self" type="application/rss+xml" />
	<link>http://securitymusings.com/article/1642/gmail-now-https-by-default</link>
	<description>Rants and raves from information security professionals</description>
	<lastBuildDate>Sat, 19 May 2012 23:32:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Oscar</title>
		<link>http://securitymusings.com/article/1642/gmail-now-https-by-default/comment-page-1#comment-25346</link>
		<dc:creator>Oscar</dc:creator>
		<pubDate>Thu, 14 Jan 2010 15:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://securitymusings.com/?p=1642#comment-25346</guid>
		<description>Twitter&#039;s initial API access which required a user to give their username and password to 3rd parties certainly was a poor security trade off.</description>
		<content:encoded><![CDATA[<p>Twitter&#8217;s initial API access which required a user to give their username and password to 3rd parties certainly was a poor security trade off.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

