<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for scottwright</title><link>http://disqus.com/by/scottwright/</link><description></description><atom:link href="http://disqus.com/scottwright/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 17 Jun 2015 05:53:23 -0000</lastBuildDate><item><title>Re: LastPass says accounts were compromised, but passwords not hacked</title><link>https://bobsullivan.net/cybercrime/privacy/lastpass-says-accounts-were-compromised-but-passwords-not-hacked/#comment-2083515788</link><description>&lt;p&gt;Good points, Bob. I agree that LastPass did a good job of responding and being transparent. However, after having had a day to think about the LastPass breach, I think it would have been a good idea for them to say in their notification email that people should be cautious about any emails from LastPass with links in them, as they could be phishing attacks. They should have said that LastPass would never send a message with a link to log in and change your password. People should use their bookmarks or type in the &lt;a href="http://LastPass.com" rel="nofollow noopener" target="_blank" title="LastPass.com"&gt;LastPass.com&lt;/a&gt; URL directly in order to change their passwords.&lt;/p&gt;&lt;p&gt;And, you are correct that it is important for people to make sure all their website passwords are strong, whether they use LastPass or not. Although, if you already have a rule of using strong passwords on sites that you store credentials for in LastPass, I don't see the need to go around changing them at this point - if the situation is as they describe it. But if you don't believe their notification's explanation of the breach, then it would obviously make you feel better to do so.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">scottwright</dc:creator><pubDate>Wed, 17 Jun 2015 05:53:23 -0000</pubDate></item><item><title>Re: Loafers? | Canucklehead.ca | Canucklehead</title><link>http://www.canucklehead.ca/look/loafers.html#comment-38946888</link><description>&lt;p&gt;Nice, but I couldn't eat them - they're just laced with sesame seeds... and they'd get all soggy when the dog brings them to me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">scottwright</dc:creator><pubDate>Wed, 10 Mar 2010 23:18:49 -0000</pubDate></item><item><title>Re: Close Knit | Canucklehead.ca | Canucklehead</title><link>http://www.canucklehead.ca/look/close_knit.html#comment-28195866</link><description>&lt;p&gt;I've been looking for some kind of security device to mitigate the risk of prying eyes while using my laptop on those super-economy, shoulder-to-shoulder flights... Found it!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">scottwright</dc:creator><pubDate>Tue, 05 Jan 2010 00:13:38 -0000</pubDate></item><item><title>Re: Mitigating Web-Based Malware Attacks</title><link>http://threatpost.com/blogs/mitigating-web-based-malware-attacks-117#comment-15017506</link><description>&lt;p&gt;Good explanations of how websites get infected.&lt;/p&gt;&lt;p&gt;Very interesting strategy for detecting and disinfecting non-malicious sites.  Too bad we need this approach so badly. Hopefully, we can start preventing website infections more effectively.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">scottwright</dc:creator><pubDate>Tue, 18 Aug 2009 12:43:18 -0000</pubDate></item></channel></rss>