<?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: Hospital resorts to Wi-Fi squatting</title> <atom:link href="http://www.kevinmd.com/blog/2007/08/hospital-resorts-to-wi-fi-squatting.html/feed" rel="self" type="application/rss+xml" /><link>http://www.kevinmd.com/blog/2007/08/hospital-resorts-to-wi-fi-squatting.html</link> <description></description> <lastBuildDate>Tue, 14 Feb 2012 21:09:00 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>By: Elliott</title><link>http://www.kevinmd.com/blog/2007/08/hospital-resorts-to-wi-fi-squatting.html#comment-79458</link> <dc:creator>Elliott</dc:creator> <pubDate>Thu, 23 Aug 2007 16:50:00 +0000</pubDate> <guid isPermaLink="false">http://clients.emmense.com/kevinmd/2007/08/hospital-resorts-to-wi-fi-squatting.html#comment-79458</guid> <description>After reading a comment on the site, I realize I did not address a third possibility that is likely, but I discounted.   Someone feels that it is neighborly or civil to leave their network open.  The problem with trusting that this is the case in any given situation is that you don&#039;t know that to be the case so you are just taking your chances.&lt;br/&gt;&lt;br/&gt;Now I do occassionally find myself in need and log on to an insecure site to check a phone number or address or send a quick email, but I never pull anything sensitive up like a bank account or my blogger password - I try for any access to be &quot;read only&quot;.  If I send email then I change my password when I get home.  Finally, I always feel a bit guilty afterwards, not for stealing bandwidth, but for taking the risk.</description> <content:encoded><![CDATA[<p>After reading a comment on the site, I realize I did not address a third possibility that is likely, but I discounted.   Someone feels that it is neighborly or civil to leave their network open.  The problem with trusting that this is the case in any given situation is that you don&#8217;t know that to be the case so you are just taking your chances.</p><p>Now I do occassionally find myself in need and log on to an insecure site to check a phone number or address or send a quick email, but I never pull anything sensitive up like a bank account or my blogger password &#8211; I try for any access to be &#8220;read only&#8221;.  If I send email then I change my password when I get home.  Finally, I always feel a bit guilty afterwards, not for stealing bandwidth, but for taking the risk.</p> ]]></content:encoded> </item> <item><title>By: Elliott</title><link>http://www.kevinmd.com/blog/2007/08/hospital-resorts-to-wi-fi-squatting.html#comment-79457</link> <dc:creator>Elliott</dc:creator> <pubDate>Thu, 23 Aug 2007 16:36:00 +0000</pubDate> <guid isPermaLink="false">http://clients.emmense.com/kevinmd/2007/08/hospital-resorts-to-wi-fi-squatting.html#comment-79457</guid> <description>Could be a HIPAA violation if any patient information is stored on that computer, but sharing an insecure Wi-Fi connection in this manner is incredibly stupid.&lt;br/&gt;&lt;br/&gt;There are only two reasons for an unsecured WI-FI site and neither bode well for this situation.  1.  The person providing the site is hopeful of capturing information that can be interesting.  The best case is that they are simply a dilletante (sp?) and the worst is that they are a potential criminal.  2.  The person provisiding the site is too clueless to understand good security practices.  This would imply (actually almost guarantee) that they may not be able to secure computers on their network properly.   This would lead to situation #1 above pretty quickly and the probability of the intruder being criminal approach 1.   &lt;br/&gt;&lt;br/&gt;I think I will click-through and contact the hospital because this is a terrible, terrible situation.  Besides having some economics expertise, (you can believe me or not) I am a data networking expert (not that you need to be an expert to be appalled at this situation).  This practice should stop immediately.</description> <content:encoded><![CDATA[<p>Could be a HIPAA violation if any patient information is stored on that computer, but sharing an insecure Wi-Fi connection in this manner is incredibly stupid.</p><p>There are only two reasons for an unsecured WI-FI site and neither bode well for this situation.  1.  The person providing the site is hopeful of capturing information that can be interesting.  The best case is that they are simply a dilletante (sp?) and the worst is that they are a potential criminal.  2.  The person provisiding the site is too clueless to understand good security practices.  This would imply (actually almost guarantee) that they may not be able to secure computers on their network properly.   This would lead to situation #1 above pretty quickly and the probability of the intruder being criminal approach 1.</p><p>I think I will click-through and contact the hospital because this is a terrible, terrible situation.  Besides having some economics expertise, (you can believe me or not) I am a data networking expert (not that you need to be an expert to be appalled at this situation).  This practice should stop immediately.</p> ]]></content:encoded> </item> <item><title>By: MLO</title><link>http://www.kevinmd.com/blog/2007/08/hospital-resorts-to-wi-fi-squatting.html#comment-79396</link> <dc:creator>MLO</dc:creator> <pubDate>Wed, 22 Aug 2007 20:54:00 +0000</pubDate> <guid isPermaLink="false">http://clients.emmense.com/kevinmd/2007/08/hospital-resorts-to-wi-fi-squatting.html#comment-79396</guid> <description>In some states this could be construed as &quot;electronic trespass.&quot;</description> <content:encoded><![CDATA[<p>In some states this could be construed as &#8220;electronic trespass.&#8221;</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using disk: enhanced
Database Caching 2/6 queries in 0.005 seconds using memcached
Object Caching 363/367 objects using apc
Content Delivery Network via cdn.kevinmd.com

Served from: www.kevinmd.com @ 2012-02-14 16:28:53 -->
