<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>boakes.org &#187; Security</title>
	<atom:link href="http://boakes.org/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://boakes.org</link>
	<description>A place for words and data that I publish (for the benefit of persons unknown).</description>
	<lastBuildDate>Wed, 08 Feb 2012 09:34:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>NHS Data Leak</title>
		<link>http://boakes.org/links/nhs-data-leak/</link>
		<comments>http://boakes.org/links/nhs-data-leak/#comments</comments>
		<pubDate>Wed, 06 Jul 2011 19:40:34 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[application]]></category>
		<category><![CDATA[apply]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[jobs]]></category>
		<category><![CDATA[leak]]></category>
		<category><![CDATA[nhs]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://boakes.org/links/nhs-data-leak/</guid>
		<description><![CDATA[A reminder that information security is not just about stopping bad guys getting in, it&#8217;s also about watching for unavoidable human error, and coping wth it.]]></description>
			<content:encoded><![CDATA[<p>A reminder that information security is not just about stopping bad guys getting in, it&#8217;s also about watching for unavoidable human error, and coping wth it.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/nhs-data-leak/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Browser Real-Time Communications</title>
		<link>http://boakes.org/links/broser-real-time-communications/</link>
		<comments>http://boakes.org/links/broser-real-time-communications/#comments</comments>
		<pubDate>Thu, 23 Jun 2011 07:53:19 +0000</pubDate>
		<dc:creator>delicious</dc:creator>
				<category><![CDATA[audio]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[compromise]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sound]]></category>
		<category><![CDATA[spy]]></category>
		<category><![CDATA[stealth]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[webcam]]></category>

		<guid isPermaLink="false">http://boakes.org/links/broser-real-time-communications/</guid>
		<description><![CDATA[So, Chrome has WebRTC, Firefox has Rainbow. Unquestionably useful, but also, highly worrying from a security perspective. If a compromised browser has unrestricted access to audio and video, then its user can be spied on.]]></description>
			<content:encoded><![CDATA[<p>So, Chrome has <a href="http://www.webrtc.org/">WebRTC</a>, Firefox has <a href="https://addons.mozilla.org/en-us/firefox/addon/mozilla-labs-rainbow/">Rainbow</a>.  Unquestionably useful, but also, highly worrying from a security perspective.  If a <em>compromised</em> browser has unrestricted access to audio and video, then its user can be spied on.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/broser-real-time-communications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WebID Primer</title>
		<link>http://boakes.org/links/webid-primer/</link>
		<comments>http://boakes.org/links/webid-primer/#comments</comments>
		<pubDate>Wed, 04 May 2011 14:21:34 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[browsers]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[openid-blogs]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[webid]]></category>

		<guid isPermaLink="false">http://boakes.org/links/webid-primer/</guid>
		<description><![CDATA[WebID proposal to enable users to retain greater control over the identity data their browsers present.]]></description>
			<content:encoded><![CDATA[<p>WebID proposal to enable users to retain greater control over the identity data their browsers present.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/webid-primer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Authentication and The Google APIs</title>
		<link>http://boakes.org/links/authentication-and-the-google-apis/</link>
		<comments>http://boakes.org/links/authentication-and-the-google-apis/#comments</comments>
		<pubDate>Wed, 16 Mar 2011 20:58:40 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[auth]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[oauth]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[user.authentication]]></category>

		<guid isPermaLink="false">http://boakes.org/links/authentication-and-the-google-apis/</guid>
		<description><![CDATA[Introduction to Google&#8217;s three main authentication systems: AuthSub, Oauth and ClientLogin.]]></description>
			<content:encoded><![CDATA[<p>Introduction to Google&#8217;s three main authentication systems: AuthSub, Oauth and ClientLogin.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/authentication-and-the-google-apis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Opt-Out Web Tracking Overview</title>
		<link>http://boakes.org/links/opt-out-web-tracking-overview/</link>
		<comments>http://boakes.org/links/opt-out-web-tracking-overview/#comments</comments>
		<pubDate>Tue, 08 Mar 2011 09:35:04 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[draft]]></category>
		<category><![CDATA[ietf]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[tracking]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://boakes.org/links/opt-out-web-tracking-overview/</guid>
		<description><![CDATA[Covers permanent opt-out cookies, cookie blocking, domain blocking, a &#8220;Do Not Track&#8221; (DNT) HTTP header, and a Do Not Track Document Object Model (DOM) property.]]></description>
			<content:encoded><![CDATA[<p>Covers permanent opt-out cookies, cookie blocking, domain blocking, a &#8220;Do<br />
   Not Track&#8221; (DNT) HTTP header, and a Do Not Track Document Object<br />
   Model (DOM) property.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/opt-out-web-tracking-overview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CORS Cross-Origin Resource Sharing</title>
		<link>http://boakes.org/links/cors-cross-origin-resource-sharing/</link>
		<comments>http://boakes.org/links/cors-cross-origin-resource-sharing/#comments</comments>
		<pubDate>Thu, 03 Feb 2011 10:37:52 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[ajax]]></category>
		<category><![CDATA[cors]]></category>
		<category><![CDATA[crossdomain]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[origin]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[XHR]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://boakes.org/links/cors-cross-origin-resource-sharing/</guid>
		<description><![CDATA[The Cross-Origin Resource Sharing working draft.]]></description>
			<content:encoded><![CDATA[<p>The Cross-Origin Resource Sharing working draft.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/cors-cross-origin-resource-sharing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open ID Is A Nightmare</title>
		<link>http://boakes.org/links/open-id-is-a-nightmare/</link>
		<comments>http://boakes.org/links/open-id-is-a-nightmare/#comments</comments>
		<pubDate>Tue, 28 Dec 2010 02:35:16 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[oauth]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://boakes.org/links/open-id-is-a-nightmare/</guid>
		<description><![CDATA[A user perspective on why OpenID can be just as complicated as (and thus, as bad as or worse than) other authentication methods.]]></description>
			<content:encoded><![CDATA[<p>A user perspective on why OpenID can be just as complicated as (and thus, as bad as or worse than) other authentication methods.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/open-id-is-a-nightmare/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HSTS &#8211; IETF Draft</title>
		<link>http://boakes.org/links/hsts-ietf-draft/</link>
		<comments>http://boakes.org/links/hsts-ietf-draft/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 20:07:49 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[hsts]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[mitm]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://boakes.org/links/hsts-ietf-draft/</guid>
		<description><![CDATA[Latest HTTP Strict Transport Security IETF draft]]></description>
			<content:encoded><![CDATA[<p>Latest HTTP Strict Transport Security IETF draft</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/hsts-ietf-draft/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>kismacng</title>
		<link>http://boakes.org/links/kismacng/</link>
		<comments>http://boakes.org/links/kismacng/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 09:25:42 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[https]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[opensource]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sniff]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[wifi]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://boakes.org/links/kismacng/</guid>
		<description><![CDATA[It&#8217;s apps like that that make it more obvious to the lay-person why secure connections are a good thing. Perfect for introductory lectures, but I&#8217;ll probably have to pass it through the ethics committee.]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s apps like that that make it more obvious to the lay-person why secure connections are a good thing.  Perfect for introductory lectures, but I&#8217;ll probably have to pass it through the ethics committee.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/kismacng/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Compromising Twitter&#8217;s OAuth security system</title>
		<link>http://boakes.org/links/compromising-twitters-oauth-security-system/</link>
		<comments>http://boakes.org/links/compromising-twitters-oauth-security-system/#comments</comments>
		<pubDate>Fri, 03 Sep 2010 06:56:57 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[compromise]]></category>
		<category><![CDATA[oauth]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://boakes.org/compromising-twitters-oauth-security-system/</guid>
		<description><![CDATA[An interesting look at Twitter&#8217;s OAuth implementation, and an attack vector based on compromising the key of an application that can be down loaded and analysed at leisure.]]></description>
			<content:encoded><![CDATA[<p>An interesting look at Twitter&#8217;s OAuth implementation, and an attack vector based on compromising the key of an application that can be down loaded and analysed at leisure.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/compromising-twitters-oauth-security-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Firefox 4: HTTP Strict Transport Security (force HTTPS)</title>
		<link>http://boakes.org/links/firefox-4-http-strict-transport-security-force-https/</link>
		<comments>http://boakes.org/links/firefox-4-http-strict-transport-security-force-https/#comments</comments>
		<pubDate>Thu, 26 Aug 2010 19:34:04 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[hsts]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://boakes.org/firefox-4-http-strict-transport-security-force-https/</guid>
		<description><![CDATA[Sid Stamm recently integrated HTTP Strict Transport Security (HSTS) into Firefox. HSTS, specified in an IETF draft, allows sites to specify when they wish to be accessed only over https.]]></description>
			<content:encoded><![CDATA[<p>Sid Stamm recently integrated HTTP Strict Transport Security (HSTS) into<br />
Firefox. HSTS, specified in an IETF draft, allows sites to specify when they wish to be accessed only over https.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/firefox-4-http-strict-transport-security-force-https/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configure Apache To Accept Cross-Site XMLHttpRequests on Ubuntu « Harth Vader&#8217;s Blog</title>
		<link>http://boakes.org/links/configure-apache-to-accept-cross-site-xmlhttprequests-on-ubuntu-%c2%ab-harth-vaders-blog/</link>
		<comments>http://boakes.org/links/configure-apache-to-accept-cross-site-xmlhttprequests-on-ubuntu-%c2%ab-harth-vaders-blog/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 00:48:42 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Access-Control-Allow-Origin]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[XHR]]></category>
		<category><![CDATA[XMLHttpRequest]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://boakes.org/configure-apache-to-accept-cross-site-xmlhttprequests-on-ubuntu-%c2%ab-harth-vaders-blog/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[]]></content:encoded>
			<wfw:commentRss>http://boakes.org/links/configure-apache-to-accept-cross-site-xmlhttprequests-on-ubuntu-%c2%ab-harth-vaders-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is the IE6 Petition News?</title>
		<link>http://boakes.org/ie6-petition/</link>
		<comments>http://boakes.org/ie6-petition/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 12:50:46 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[downing street]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[swiss cheese]]></category>

		<guid isPermaLink="false">http://boakes.org/?p=1263</guid>
		<description><![CDATA[BBC News has a front page story about a petition to the government to phase out the use of IE6. Historically, ceasing to use IE has always been a good idea in my book, and IE6 is now very outdated (it&#8217;ll be nine years old in August). What caught my eye, however, was the following [...]]]></description>
			<content:encoded><![CDATA[<p>BBC News has <a href="http://news.bbc.co.uk/1/hi/technology/8492862.stm">a front page story</a> about <a href="http://petitions.number10.gov.uk/ie6upgrade/">a petition to the government to phase out the use of IE6</a>.  Historically, ceasing to use IE has always been a good idea in my book, and IE6 is now very outdated (it&#8217;ll be nine years old in August).  What caught my eye, however, was the following line in the article, removed from later editions: </p>
<blockquote><p>&#8220;The petition, set up by Dan Frydman of web firm Inigo, currently has just 44 signatures.&#8221;</p></blockquote>
<p>Since when is a petition with 44 signatures worthy of front page BBC News?  Does someone in their web team have an undisclosed anti-IE6 agenda, or has the Beeb started doing marketing work on the side?</p>
<p>Since the BBC story was posted, the petition has gained approximately 1300 signatures.</p>
<p><strong>Update:</strong> 11 hours later and the petition has 4400 signatures.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/ie6-petition/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Credit Card Phone Security</title>
		<link>http://boakes.org/cc-phone-sec/</link>
		<comments>http://boakes.org/cc-phone-sec/#comments</comments>
		<pubDate>Sun, 27 Nov 2005 18:57:26 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://boakes.org/lightning-struck</guid>
		<description><![CDATA[Last week I received a replacement credit card. Attached to the card was a sticker, telling me that I had to call the company so that they could register it&#8217;s safe arrival and enable it for my use. I called them immediately and we went through the usual security shenanigens (inside leg measurement, favourite adverb, [...]]]></description>
			<content:encoded><![CDATA[<p>Last week I received a replacement credit card.  Attached to the card was a sticker, telling me that I had to call the company so that they could register it&#8217;s safe arrival and enable it for my use.</p>
<p>I called them immediately and we went through the usual security shenanigens (inside leg measurement, favourite adverb, etc) and the card was activated.<span id="more-311"></span></p>
<p>A couple of minutes after my activation call I received a phonecall from a lady who claimed to be from the same credit card company, saying that she had to confirm who she was talking to before she could tell me <em>something very important</em> about my credit card.</p>
<p>She asked me all the security questions, and this time I refused to answer.</p>
<p>I explained to her that she could have been anyone, so I asked her to prove her identity by telling me something that only the two of us could know, something from my account or something about my previous phonecall.  She said she couldn&#8217;t because of the data protection act.  So I took her name and extension number, and called her back on the standard company number.</p>
<p>Telephone security in this credit card company is fundamentally flawed.  Their policy of calling customers without a means of self authentication whilst asking customers to provide personal information as an authentication token results in an overall reduction in the security of their cardholders.</p>
<p>The recent spate of <a href="http://en.wikipedia.org/wiki/Phishing">phishing</a> has led to many banks and credit providers issuing warnings about not giving out your personal details online, yet this is an example of a company that&#8217;s normalising the process of giving away your credentials to an unauthenticated party through their own actions.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/cc-phone-sec/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Chips, PINs and Security Cameras</title>
		<link>http://boakes.org/chip-pin-camera/</link>
		<comments>http://boakes.org/chip-pin-camera/#comments</comments>
		<pubDate>Sat, 17 Sep 2005 14:35:54 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Society]]></category>

		<guid isPermaLink="false">http://boakes.org/?p=480</guid>
		<description><![CDATA[My local convenience store is typical of any corner store; there&#8217;s perhaps 100 square meters of shop space, with security cameras at the end of each aisle and (as featured on every smash-and-grab TV show) extra cameras focused on the checkout. The cameras curtail shoplifting, and the new Chip and PIN payment system reduces fraud. [...]]]></description>
			<content:encoded><![CDATA[<p>My local convenience store is typical of any corner store; there&#8217;s perhaps 100 square meters of shop space, with security cameras at the end of each aisle and (as featured on every <em>smash-and-grab</em> TV show) extra cameras focused on the checkout.  The cameras curtail shoplifting, and the new <a href="http://en.wikipedia.org/wiki/Chip_and_pin">Chip and PIN</a> payment system reduces fraud.  The shopkeepers are happy because their livelyhood is better protected, however, as I was buying milk this morning, I realised that these two security measures may have an <em><strong>unwanted</strong> overlap</em> that could leave the customer less protected.<span id="more-480"></span></p>
<p>Recent articles by <a href="http://www.guardian.co.uk/crime/article/0,2763,1562681,00.html">the Guardian</a>, <a href="http://news.bbc.co.uk/2/hi/science/nature/4213848.stm">the BBC</a>, <a href="http://www.theregister.co.uk/2005/09/05/hi-tech_id_theft_cure_fallacy/">the Register</a> and <a href="http://www.schneier.com/blog/archives/2005/09/identity_cards.html">Bruce Schneier</a> have highlighted some insight provided by  <a href="http://www.uea.ac.uk/law/people/emily_finch.htm">Dr. Emily Finch</a>&#8216;s interviews with credit card criminals:</p>
<blockquote><p>&#8220;One of the things that is very clear is that it is a difficult matter for a fraudster to get hold of somebody&#8217;s card and then find out the PIN.  So the focus has been changed to finding the PIN first, which is very, very easy if you are prepared to break social convention and look when people type the number in at the point of sale &#8230; and then attempt to steal the card at a later date.&#8221;</p></blockquote>
<p>To combat such social miscreants, the <em>Chip and PIN</em> machine that&#8217;s installed in my local store (pictured) features a small finger shield that can partially obscure the view of a ne&#8217;er-do-well who has to be looking at just the right moment to be able to spot the PIN.</p>
<p><img class="soloimg" src="/pics/2005/chipandpin/chipandpin.png" alt="Chip and Pin Machine" /></p>
<p>The effectiveness of this shield is largely compromised, however, because <strong>the checkout camera stays squarely focused on the customer, and their PIN</strong>, even when everybody else <em>does</em> avert their gaze: so <strong>anybody that has access to the shop&#8217;s security recordings</strong> doesn&#8217;t need furtive glances, they <strong>can take their time and study every delicate finger movement as the PIN is entered</strong>.</p>
<p>If this is not happening already, it will, I guarantee it.</p>
<p>Today the resolution on most ageing surveillance cameras is unlikely to be high enough to enable a frame-by-frame zoomed analysis of how a shoppers fingers move as they type their PIN, but, that&#8217;s changing, because of the rapidly decreasing cost of low and mid-range digital imaging equipment.  The future of digital surveilance is crisp focused pictures, that can get a very good closeup of any keypad.</p>
<p>Next time you use your <em>chip and PIN</em> card, take a look around and see if you&#8217;re being recorded.  Ask the shopkeeper about who has access to the security tapes.</p>
<p>I asked at my local store (purely out of interest) and was met with an open mouthed &#8220;Uh?&#8221;.</p>
<p>If you&#8217;d like to take the investigation further in the UK, then the Data Protection Act (DPA) provides for a useful means of gathering material that can illustrate the problem.  The DPA grants <a href="http://www.informationcommissioner.gov.uk/cms/DocumentUploads/subject%20access%20faq.pdf">the subject</a> of any CCTV recording access to &#8220;the information held about them, a description of why that information is being processed, and details of anyone who may see a copy of the data, to whom it may be transferred, and the logic involved in any automated decisions taken on the basis of that data.&#8221;  So for the cost of a stamp, and a maximum fee of Â£10, it&#8217;s possible to get a copy of the recording, and see for yourself whether your PIN is decipherable.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/chip-pin-camera/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Spammed by MyNiceMailAt .com</title>
		<link>http://boakes.org/my-nice-spam-domain/</link>
		<comments>http://boakes.org/my-nice-spam-domain/#comments</comments>
		<pubDate>Sat, 17 Sep 2005 11:00:14 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Society]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://boakes.org/?p=481</guid>
		<description><![CDATA[Hopefully I just spoiled a spammer&#8217;s whole week. How? I bought the domain that he&#8217;s trying to promote (MyNiceMailAt.com) before he did. When I receive comment spam which doesn&#8217;t obviously link to a gambling, pornographic or pharmaceutical site then I usually do a little investigation to see what&#8217;s on the site, who owns it, why [...]]]></description>
			<content:encoded><![CDATA[<p>Hopefully I just spoiled a spammer&#8217;s whole week.  How?  I bought the domain that he&#8217;s trying to promote (<em>MyNiceMailAt.com</em>) before he did.<span id="more-481"></span></p>
<p>When I receive comment spam which doesn&#8217;t obviously link to a gambling, pornographic or pharmaceutical site then I usually do a little investigation to see what&#8217;s on the site, who owns it, why they&#8217;re spamming me, etc.</p>
<p>In the last 24 hours I&#8217;ve been hit by comment spam promoting <em>MyNiceMailAt.com</em>.</p>
<ol>
<li>I tried to look at <em>mynicemailat.com</em>, and it didn&#8217;t exist; so</li>
<li>I tried to find the domain ownership records, and they didn&#8217;t exist either.</li>
</ol>
<p><em>MyNiceMailAt.com</em> was an unregistered domain, being promoted by a spammer.</p>
<ol>
<li>I like to do my bit for hindering spammers; so</li>
<li>I bought the domain, before the spammer could; so</li>
<li>the entire spam run has been a waste of the spammer&#8217;s time and resources.</li>
</ol>
<h3>Useful Info</h3>
<ul>
<li>If you&#8217;d like to learn more about comment spam, I highly recommend Ann Elisabeth&#8217;s <a href="http://spamhuntress.com/">SpamHuntress</a> blog.</li>
<li>This is not the first time such action has been taken by a spam recipient, last year <a href="http://jagk.com">jagk.com</a> was similarly snapped up, and now has a regularly updated <a href="http://jagk.com/htaccess.txt">spam blacklist</a> that you can add to your .htaccess file (if you don&#8217;t run your blog server, tell your administrator about it).</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/my-nice-spam-domain/feed/</wfw:commentRss>
		<slash:comments>42</slash:comments>
		</item>
		<item>
		<title>Bad-guys, 1, Good Guys, nil.</title>
		<link>http://boakes.org/one-nil/</link>
		<comments>http://boakes.org/one-nil/#comments</comments>
		<pubDate>Wed, 23 Mar 2005 16:28:18 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://boakes.org/one-nil</guid>
		<description><![CDATA[Reverse engineering of a real world object like the Eiffel Tower, would require a few theodolites, perhaps a tape measure or two and a big sheet of paper, in order to create a set of blueprints from which an identical tower could be built. In computing, it&#8217;s a simlar process, the low level computer code [...]]]></description>
			<content:encoded><![CDATA[<p>Reverse engineering of a real world object like the Eiffel Tower, would require a few theodolites, perhaps a tape measure or two and a big sheet of paper, in order to create a set of blueprints from which an identical tower could be built.<span id="more-230"></span></p>
<p>In computing, it&#8217;s a simlar process, the low level computer code that makes up a program can be turned into higher level code that humans find more palatable.  The result, is a set of &#8220;blueprints&#8221; that allow an experienced software engineer to go beyond an understanding of <em>what a program does</em>; they know <em>how the program does it</em> .</p>
<p>Legally, this has been a grey area for some time.  Although there are commercial &#038; contractural technicalities that make reverse enginering code &#8220;a little bit illegal&#8221;, there are some important benefits.</p>
<p>To understand the benefits it&#8217;s first necessary to accept that there are some people in the world who are inherently naughty, and who will therefore reverse engineer code, and exploit any weakness they find &#8211; <strong>because they can, and because they <em>don&#8217;t</em> care about the consequences</strong>.  Typically, an exploitable weakness will be something very simple that enables an attacker to gain control of a machine.</p>
<p>There are an opposing group of noble, unsung-superhero-type-good-guys who also reverse engineer stuff, but they don&#8217;t do bad things with it.   Instead they analyse the vulnerabilities of many different pieces of software, and improve the process of software engineering by talking about the problems they see &#8211; <strong>because they can, and becasue they <em>do</em> care about the consequences.</strong></p>
<p>Today, a French court has convicted a security researcher (one of the people in the second group) and dished out a â‚¬5000 suspended fine for the crime of reverse engineering an anti-virus product which he proved was open to exploitation.</p>
<p>So &#8211; all French superheroes are now open to large fines if they publish their findings.  This means that they won&#8217;t publish.  This will do nothing to stop the naughty people from reverse engineering software and exploiting the weaknesses, but it will stop the software manufacturers from improving their code, because the flaws won&#8217;t be found, not in France anyway.</p>
<p><em>Zoot alors.</em></p>
<p>Bad-guys, 1, Good Guys, nil.</p>
]]></content:encoded>
			<wfw:commentRss>http://boakes.org/one-nil/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

