<div>I believe that most cases of email &quot;hacking&quot; are going to be like this, where a security question &quot;whats my favorite cat&#39;s name&quot; is easily answered by going to someone&#39;s flickr page.</div>
<div> </div>
<div>kudos to that &quot;hacker&quot;, and shame on the accound owner.  Again, I don&#39;t care about &quot;attacks&quot; like these.  The day I read about gmail being attacked because of some combination MITM, XSS, and GPG flaw (for when it supports it in the future /want), then I get worried and care.</div>

<div> </div>
<div>bigjust<br><br></div>
<div class="gmail_quote">On Mon, Jul 20, 2009 at 11:57 AM, William Fragakis <span dir="ltr">&lt;<a href="mailto:william@fragakis.com">william@fragakis.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><a href="http://www.computerworld.com/s/article/9135661/Report_Hacker_broke_into_Twitter_e_mail_with_help_from_Hotmail" target="_blank">http://www.computerworld.com/s/article/9135661/Report_Hacker_broke_into_Twitter_e_mail_with_help_from_Hotmail</a><br>

<div>
<div></div>
<div class="h5"><br><br><br>On Thu, 2009-07-16 at 13:32 -0400, justin caratzas wrote:<br>&gt; Correct me if I&#39;m wrong Jim, but I think he means we need to separate<br>&gt; a service being hacked from an individual account being hacked.<br>
&gt;<br>&gt; In this case, an account was hacked, and boo-hoo on the account holder<br>&gt; for picking loose security questions, or whatever it was.  GMail as a<br>&gt; service was not hacked, which in that case it would affect everyone.<br>
&gt;<br>&gt; bigjust<br>&gt;<br>&gt;<br>&gt; On Thu, Jul 16, 2009 at 1:19 PM, Jeff Lightner &lt;<a href="mailto:jlightner@water.com">jlightner@water.com</a>&gt;<br>&gt; wrote:<br>&gt;         Did my post affect you?<br>&gt;<br>
&gt;<br>&gt;         -----Original Message-----<br>&gt;         From: <a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a> [mailto:<a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a>] On<br>&gt;         Behalf Of Jim<br>
&gt;         Popovitch<br>&gt;         Sent: Thursday, July 16, 2009 12:17 PM<br>&gt;         To: Atlanta Linux Enthusiasts - Yes! We run Linux!<br>&gt;         Subject: [ale] &quot;hacked&quot; (was: gmail then Google Apps hacked)<br>
&gt;<br>&gt;         On Thu, Jul 16, 2009 at 05:59, Jeff<br>&gt;         Lightner&lt;<a href="mailto:jlightner@water.com">jlightner@water.com</a>&gt; wrote:<br>&gt;         &gt; One reason why Google Apps and cloud computing isn&#39;t such a<br>
&gt;         great<br>&gt;         idea:<br>&gt;<br>&gt;         The word &quot;hacked&quot; has different meanings to different people.<br>&gt;          I&#39;m a<br>&gt;         gmail user and I don&#39;t feel that the past &quot;hacking&quot; incident<br>
&gt;         affected<br>&gt;         me one bit.  In fact an outage would be a bigger pain, but not<br>&gt;         so<br>&gt;         great to justify building/maintaining my own infrastructure.<br>&gt;<br>&gt;         Did the gmail hack or twitter hack affect you?<br>
&gt;<br>&gt;         -Jim P.<br>&gt;<br>&gt;         _______________________________________________<br>&gt;         Ale mailing list<br>&gt;         <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>&gt;         <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
&gt;<br>&gt;<br>&gt;         Please consider our environment before printing this e-mail or<br>&gt;         attachments.<br>&gt;         ----------------------------------<br>&gt;         CONFIDENTIALITY NOTICE: This e-mail may contain privileged or<br>
&gt;         confidential information and is for the sole use of the<br>&gt;         intended recipient(s). If you are not the intended recipient,<br>&gt;         any disclosure, copying, distribution, or use of the contents<br>
&gt;         of this information is prohibited and may be unlawful. If you<br>&gt;         have received this electronic transmission in error, please<br>&gt;         reply immediately to the sender that you have received the<br>
&gt;         message in error, and delete it. Thank you.<br>&gt;         ----------------------------------<br>&gt;<br>&gt;<br>&gt;         _______________________________________________<br>&gt;         Ale mailing list<br>
&gt;         <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>&gt;         <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>&gt;<br>&gt;<br>&gt; _______________________________________________<br>
&gt; Ale mailing list<br>&gt; <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>&gt; <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br><br>_______________________________________________<br>
Ale mailing list<br><a href="mailto:Ale@ale.org">Ale@ale.org</a><br><a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br></div></div></blockquote></div><br>