<?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/"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:media="http://search.yahoo.com/mrss/"
> <channel><title>Comments on: Google Calendar Security Notice</title> <atom:link href="http://chris.pirillo.com/google-calendar-security-notice/feed/" rel="self" type="application/rss+xml" /><link>http://chris.pirillo.com/google-calendar-security-notice/</link> <description>News and Reviews! Geek, Internet Entrepreneur, Hardware Addict, Software Junkie, Book Author, Once TV Show Host, Technology Enthusiast, Shameless Self-Promoter, Tech Conference Coordinator, Early Adopter, Idea Evangelist, Tech Support Blogger, Bootstrapper, Media Personality, Technology Consultant, Thicker Quicker Picker Upper.</description> <lastBuildDate>Mon, 23 Nov 2009 01:37:17 -0800</lastBuildDate> <generator>http://wordpress.org/?v=2.8.5</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Is Google Calenda Secure? :Search Engine News</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-328320</link> <dc:creator>Is Google Calenda Secure? :Search Engine News</dc:creator> <pubDate>Wed, 25 Apr 2007 13:53:23 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-328320</guid> <description>[...] Chris Pirillo has discovered that if you search for public documents in Googles online calendar, you will be presented with [...]</description> <content:encoded><![CDATA[<p>[...] Chris Pirillo has discovered that if you search for public documents in Googles online calendar, you will be presented with [...]</p> ]]></content:encoded> </item> <item><title>By: Login Credentials in Public Google Calendars &#171; Know what is happening throughout the world</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-323323</link> <dc:creator>Login Credentials in Public Google Calendars &#171; Know what is happening throughout the world</dc:creator> <pubDate>Tue, 24 Apr 2007 05:56:53 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-323323</guid> <description>[...] Startup Meme and Chris Pirillo report that quite a few people have made login credentials of theirs public via Google Calendar event descriptions, which can now be found by searching for public events for e.g. “username password”. When you create a calendar with Google, you have the options “do not share with everyone” (default) and “share all information on this calendar with everyone” (which additionally triggers a confirmation dialog). However, when people add certain events to public calendars, it may be that they’ve forgotten they once made the calendar public. Maybe Google needs to put a more visible icon next to public calendars as a reminder, or always trigger a confirmation when you add an event to a public calendar, but this is not a Google Calendar security vulnerability – it’s user misconfiguration, similar to when you e.g. create a blog post with information that ought to be secret, and then someone searches Google for “password username”. [...]</description> <content:encoded><![CDATA[<p>[...] Startup Meme and Chris Pirillo report that quite a few people have made login credentials of theirs public via Google Calendar event descriptions, which can now be found by searching for public events for e.g. “username password”. When you create a calendar with Google, you have the options “do not share with everyone” (default) and “share all information on this calendar with everyone” (which additionally triggers a confirmation dialog). However, when people add certain events to public calendars, it may be that they’ve forgotten they once made the calendar public. Maybe Google needs to put a more visible icon next to public calendars as a reminder, or always trigger a confirmation when you add an event to a public calendar, but this is not a Google Calendar security vulnerability – it’s user misconfiguration, similar to when you e.g. create a blog post with information that ought to be secret, and then someone searches Google for “password username”. [...]</p> ]]></content:encoded> </item> <item><title>By: Calgoo</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-321543</link> <dc:creator>Calgoo</dc:creator> <pubDate>Mon, 23 Apr 2007 22:15:01 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-321543</guid> <description>We at the Calgoo office use Google Calendar for business purposes.  After spending so much time with it its hard to imagine someone making this mistake.  That said it is clearly a case of user eduction - or lack there of.  The only problem is how far must one go to educate their users before some are turned off by feeling patronized.- Calgoo
www.calgoo.com</description> <content:encoded><![CDATA[<p>We at the Calgoo office use Google Calendar for business purposes.  After spending so much time with it its hard to imagine someone making this mistake.  That said it is clearly a case of user eduction &#8211; or lack there of.  The only problem is how far must one go to educate their users before some are turned off by feeling patronized.</p><p>- Calgoo<br
/> <a
href="http://www.calgoo.com" rel="nofollow">http://www.calgoo.com</a></p> ]]></content:encoded> </item> <item><title>By: Google Calendar Passwords in The Open, Google Antitrust case, and more Google News</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-321164</link> <dc:creator>Google Calendar Passwords in The Open, Google Antitrust case, and more Google News</dc:creator> <pubDate>Mon, 23 Apr 2007 20:49:05 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-321164</guid> <description>[...] Google Calendar Security Notice Uh, guys… y’all gotta tell your friends not to store usernames and passwords in public documents - at least, not without protecting them with passwords themselves. More importantly, the last thing you want to do is set a reminder for yourself in Google Calendar and leave the login credentials in the reminder AND set it for public viewing. [...]</description> <content:encoded><![CDATA[<p>[...] Google Calendar Security Notice Uh, guys… y’all gotta tell your friends not to store usernames and passwords in public documents &#8211; at least, not without protecting them with passwords themselves. More importantly, the last thing you want to do is set a reminder for yourself in Google Calendar and leave the login credentials in the reminder AND set it for public viewing. [...]</p> ]]></content:encoded> </item> <item><title>By: Mosuki blog &#187; Google calendar: sharing gone wild!</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-321002</link> <dc:creator>Mosuki blog &#187; Google calendar: sharing gone wild!</dc:creator> <pubDate>Mon, 23 Apr 2007 20:04:45 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-321002</guid> <description>[...] We posted eight months ago about Google calendar&#8217;s lack of respect for private data. Chris Pirillo has a found a clever demonstration of this: just search for &#8220;user password&#8221; in public events, and you&#8217;ll come up with a huge list of usernames and passwords of all sorts. [...]</description> <content:encoded><![CDATA[<p>[...] We posted eight months ago about Google calendar&#8217;s lack of respect for private data. Chris Pirillo has a found a clever demonstration of this: just search for &#8220;user password&#8221; in public events, and you&#8217;ll come up with a huge list of usernames and passwords of all sorts. [...]</p> ]]></content:encoded> </item> <item><title>By: Greg</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-320592</link> <dc:creator>Greg</dc:creator> <pubDate>Mon, 23 Apr 2007 18:17:15 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-320592</guid> <description>I think Google should probably notify folks.  It&#039;s not their fault, but they&#039;d look bad if there were a hack.</description> <content:encoded><![CDATA[<p>I think Google should probably notify folks.  It&#8217;s not their fault, but they&#8217;d look bad if there were a hack.</p> ]]></content:encoded> </item> <item><title>By: Easton Ellsworth</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-320130</link> <dc:creator>Easton Ellsworth</dc:creator> <pubDate>Mon, 23 Apr 2007 15:56:02 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-320130</guid> <description>Er, to elaborate - that&#039;s both amazing and ho-hum - I mean of course there would be a great many uneducated or un-forewarned GCal users out there - but the sheer volume of it amazes me.  Thanks for the heads-up Chris and Michael.</description> <content:encoded><![CDATA[<p>Er, to elaborate &#8211; that&#8217;s both amazing and ho-hum &#8211; I mean of course there would be a great many uneducated or un-forewarned GCal users out there &#8211; but the sheer volume of it amazes me.  Thanks for the heads-up Chris and Michael.</p> ]]></content:encoded> </item> <item><title>By: Easton Ellsworth</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-320120</link> <dc:creator>Easton Ellsworth</dc:creator> <pubDate>Mon, 23 Apr 2007 15:54:47 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-320120</guid> <description>Dude.</description> <content:encoded><![CDATA[<p>Dude.</p> ]]></content:encoded> </item> <item><title>By: Google Calendar Security Notice &#124; TomCoyote</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-319575</link> <dc:creator>Google Calendar Security Notice &#124; TomCoyote</dc:creator> <pubDate>Mon, 23 Apr 2007 14:09:29 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-319575</guid> <description>[...] Via: Chris.Pirillo.com [...]</description> <content:encoded><![CDATA[<p>[...] Via: <a
href="http://Chris.Pirillo.com" title="http://Chris.Pirillo.com" target="_blank">Chris.Pirillo.com</a> [...]</p> ]]></content:encoded> </item> <item><title>By: MAcsSNAcs</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-319514</link> <dc:creator>MAcsSNAcs</dc:creator> <pubDate>Mon, 23 Apr 2007 13:56:44 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-319514</guid> <description>What I don&#039;t understand is why the default isn&#039;t private, and you change it top public if you want... Wouldn&#039;t that be the easiest solution. I hate having to make private things private. I don&#039;t use the calendar to share things... yet, just to keep track for myself.</description> <content:encoded><![CDATA[<p>What I don&#8217;t understand is why the default isn&#8217;t private, and you change it top public if you want&#8230; Wouldn&#8217;t that be the easiest solution. I hate having to make private things private. I don&#8217;t use the calendar to share things&#8230; yet, just to keep track for myself.</p> ]]></content:encoded> </item> <item><title>By: Google Calendar Users Sharing Their Passwords &#124; Marketing Pilgrim</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-319293</link> <dc:creator>Google Calendar Users Sharing Their Passwords &#124; Marketing Pilgrim</dc:creator> <pubDate>Mon, 23 Apr 2007 13:14:43 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-319293</guid> <description>[...] Chris Pirillo has a community announcement for anyone using Google Calendar. He warns that some users are inadvertently storing their usernames and passwords in Google Calendar, while sharing their calendar with the world wide web. Google has just created an enormous security problem. [...]</description> <content:encoded><![CDATA[<p>[...] Chris Pirillo has a community announcement for anyone using Google Calendar. He warns that some users are inadvertently storing their usernames and passwords in Google Calendar, while sharing their calendar with the world wide web. Google has just created an enormous security problem. [...]</p> ]]></content:encoded> </item> <item><title>By: Bill</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-319208</link> <dc:creator>Bill</dc:creator> <pubDate>Mon, 23 Apr 2007 12:59:05 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-319208</guid> <description>I&#039;m failing to see how Google creates this problem. When people are dumb enough to put passwords on public documents, they get what they get. Perhaps Google could put a few more warnings up, though.</description> <content:encoded><![CDATA[<p>I&#8217;m failing to see how Google creates this problem. When people are dumb enough to put passwords on public documents, they get what they get. Perhaps Google could put a few more warnings up, though.</p> ]]></content:encoded> </item> <item><title>By: Bruce Boughton</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-319154</link> <dc:creator>Bruce Boughton</dc:creator> <pubDate>Mon, 23 Apr 2007 12:48:06 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-319154</guid> <description>This reminds me of a recent spot on Virgin Radio here in the UK.  Virgin Radio ran a competition where, if you revealed to them your work logon and password, you won a prize.  Surprising numbers of people did!  A similar experiment also showed people would hand over their logon and password for a free plastic biro pen!  Madness!</description> <content:encoded><![CDATA[<p>This reminds me of a recent spot on Virgin Radio here in the UK.  Virgin Radio ran a competition where, if you revealed to them your work logon and password, you won a prize.  Surprising numbers of people did!  A similar experiment also showed people would hand over their logon and password for a free plastic biro pen!  Madness!</p> ]]></content:encoded> </item> <item><title>By: Paul Stewart</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-319038</link> <dc:creator>Paul Stewart</dc:creator> <pubDate>Mon, 23 Apr 2007 12:25:33 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-319038</guid> <description>It is interesting, for all the folks in the geek world who know how to do things for themselves, geeks are lazy/cheep to rely on free services ment for the brain dead. And because it is Google, friend of open source, free software (as in freedom,) the alternative to the MS Monopoly, savior to the average user, brilliant minds, you have to ask; Is it on purpose? Have we all learned our lesson? This hasn&#039;t just happened to average users.This is what Google thinks of you.</description> <content:encoded><![CDATA[<p>It is interesting, for all the folks in the geek world who know how to do things for themselves, geeks are lazy/cheep to rely on free services ment for the brain dead. And because it is Google, friend of open source, free software (as in freedom,) the alternative to the MS Monopoly, savior to the average user, brilliant minds, you have to ask; Is it on purpose? Have we all learned our lesson? This hasn&#8217;t just happened to average users.</p><p>This is what Google thinks of you.</p> ]]></content:encoded> </item> <item><title>By: Metablogging.gr &#187; Google Calendar: Προσοχή. Τεράστιο θέμα ασφάλειας</title><link>http://chris.pirillo.com/google-calendar-security-notice/comment-page-1/#comment-318759</link> <dc:creator>Metablogging.gr &#187; Google Calendar: Προσοχή. Τεράστιο θέμα ασφάλειας</dc:creator> <pubDate>Mon, 23 Apr 2007 11:33:21 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2007/04/22/google-calendar-security-notice/#comment-318759</guid> <description>[...] Η είδηση από το blog του Chis Pirillo που μου υπέδειξε ο basileios. [...]</description> <content:encoded><![CDATA[<p>[...] Η είδηση από το blog του Chis Pirillo που μου υπέδειξε ο basileios. [...]</p> ]]></content:encoded> </item> </channel> </rss><!--
This site's performance optimized by W3 Total Cache:

W3 Total Cache improves the user experience of your blog by caching
frequent operations, reducing the weight of various files and providing
transparent content delivery network integration.

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached
Page Caching using memcached
Database Caching 12/35 queries in 0.071 seconds using memcached
Content Delivery Network via maxcdn.chris.pirillo.com

Served from: 192.168.20.62 @ 2009-11-24 20:59:16 -->