<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

      <title>Comments on: Next step, X-ray specs!</title>
      <link>http://www.metafilter.com/33065/Next-step-Xray-specs/</link>
      <description>Comments on MetaFilter post Next step, X-ray specs!</description>
	  	  <pubDate>Thu, 13 May 2004 00:36:45 -0800</pubDate>
      <lastBuildDate>Thu, 13 May 2004 00:36:45 -0800</lastBuildDate>
      <language>en-us</language>
	  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
	  <ttl>60</ttl>

<item>
  	<title>Next step, X-ray specs!</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs</link>	
    <description>A CS grad student comes up with a technique for restoring words that have been blacked out in classified documents. </description>
  	<guid isPermaLink="false">post:www.metafilter.com,2008:site.33065</guid>
  	<pubDate>Thu, 13 May 2004 00:35:40 -0800</pubDate>
  	<dc:creator>nomis</dc:creator>
	
	<category>technology</category>
	
	<category>classified</category>
	
	<category>documents</category>
	
	<category>brokenlink</category>
	
</item>
<item>
  	<title>By: nomis</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669720</link>	
    <description>What I find interesting is that this technique still boils down to picking the best candidate from a potential bunch of solutions. Surely that limits the applicability?

For example, the text gives a test case in which &quot;Egyptian&quot; is picked as the best fit, but I can&apos;t help thinking that &quot;unofficial&quot; would be just as good a fit.

And what if the censored portions were people&apos;s names? They wouldn&apos;t be in an electronic dictionary.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669720</guid>
  	<pubDate>Thu, 13 May 2004 00:36:45 -0800</pubDate>
  	<dc:creator>nomis</dc:creator>
</item>
<item>
  	<title>By: Space Coyote</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669722</link>	
    <description>&lt;i&gt;And what if the censored portions were people&apos;s names? They wouldn&apos;t be in an electronic dictionary.&lt;/i&gt;

It&apos;s not much more computing power to add in a list of names and even to just list all possibilities and then filter out never-used letter combinations to produce phoenetically possible words.

I find it funniest that it only works now that the state department mandated a shift from a monospace font to a proportional font.   You&apos;d  think someone in charge should have thought of this.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669722</guid>
  	<pubDate>Thu, 13 May 2004 00:42:10 -0800</pubDate>
  	<dc:creator>Space Coyote</dc:creator>
</item>
<item>
  	<title>By: Gyan</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669727</link>	
    <description>I see an easy solution to this. If a classified document needs to be released, all the blacklist candidates should be normalized to, say, 24 characters, by prefixing and suffixing some standard strings.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669727</guid>
  	<pubDate>Thu, 13 May 2004 01:15:17 -0800</pubDate>
  	<dc:creator>Gyan</dc:creator>
</item>
<item>
  	<title>By: angry modem</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669752</link>	
    <description>There was a way to do this through a flaw in PDF documents some time ago.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669752</guid>
  	<pubDate>Thu, 13 May 2004 04:43:05 -0800</pubDate>
  	<dc:creator>angry modem</dc:creator>
</item>
<item>
  	<title>By: effugas</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669755</link>	
    <description>The flaw in PDF docs was because they were just overlaying a big black square on top of whatever Acrobat was supposed to display.  People just removed the black block from the PDF and poof.

This involves actually reversing a fully blocked out section, based on its width.  It&apos;s really quite brilliantly done -- and as Space Coyote points out, it&apos;s made a thousand times easier with proportional fonts -- given characters of 5, 3.3, 4, 2.2, 7.1, and 4.6mm, there&apos;s only one set of characters that can yield a blot out of 16.1mm, and very few relevant words that can be spelled with those characters.  Wow.  We should have known.

To be fair, I noticed the original announcement that State was changing its fonts, and I didn&apos;t even imagine that there might be a security implication in that.  Definite &quot;obvious in retrospect&quot;.

Regarding blacklisting, changing spacing of a document is enormously tricky -- adjust something on one page, and everything else repaginates.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669755</guid>
  	<pubDate>Thu, 13 May 2004 05:00:22 -0800</pubDate>
  	<dc:creator>effugas</dc:creator>
</item>
<item>
  	<title>By: chrismear</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669757</link>	
    <description>But when you blot out a word manually with a marker pen, surely you don&apos;t block out &lt;i&gt;precisely&lt;/i&gt; the width that the characters take up. Isn&apos;t the black mark likely to be slightly longer than the actual word blocked out -- and a random amount longer, at that? How does this technique take account of that?</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669757</guid>
  	<pubDate>Thu, 13 May 2004 05:14:19 -0800</pubDate>
  	<dc:creator>chrismear</dc:creator>
</item>
<item>
  	<title>By: nylon</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669760</link>	
    <description>everything on the same line of text should be equally spaced, chrismear - measure the distance between the end of the preceeding word and the start of the following word, subtract two lots of space, and there you have the exact length. although of course this fails if you marker pen over two or more consecutive words. then it gets tricky.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669760</guid>
  	<pubDate>Thu, 13 May 2004 05:28:47 -0800</pubDate>
  	<dc:creator>nylon</dc:creator>
</item>
<item>
  	<title>By: luser</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669780</link>	
    <description>Much of the redacting I&apos;ve seen is long strings of words, very commonly entire paragraphs. This technique is of limited use. 

However, this brings up a point that&apos;s bothered me since around 9/11: Shouldn&apos;t there be a cabinet-level IT department in the U.S. Government? Not that I&apos;d want the job, but it seems like there&apos;s all kinds of efficiency, cost, and, especially, national security advantages to the governement using up-to-date, interoperable technology. 

Every time I see evidence of the tech savvy  of the U.S. government, compared to that of the typical 14-year old, I wince. Redacted classified info with sharpies is just the tip of the iceberg.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669780</guid>
  	<pubDate>Thu, 13 May 2004 06:21:23 -0800</pubDate>
  	<dc:creator>luser</dc:creator>
</item>
<item>
  	<title>By: signal</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669788</link>	
    <description>If the researchers were in the US, they&apos;d probably be answering questions from a judge, right about now.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669788</guid>
  	<pubDate>Thu, 13 May 2004 06:33:16 -0800</pubDate>
  	<dc:creator>signal</dc:creator>
</item>
<item>
  	<title>By: zaelic</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669809</link>	
    <description>When I worked as a bookbinder / preservationist at BU Mugar Libraries, we would sometimes receive books for the African Studies Library from South Africa or Rhodesia (this was the &apos;70s) that had blacked out passages, using thickened india ink. Almost impossible to remove. We tried all kinds of solvents. Occasionally we succeeded in getting a bit of the ink off. Usually it was a reference to a &quot;banned&quot; person, Steven Biko in one case we worked on. 

It&apos;s interesting that right-wing governments would black out passages in published books, while in communist countries the solution was much easier - they simply banned the book and jailed the writers (at least here in Hungary.)

&lt;em&gt;However, this brings up a point that&apos;s bothered me since around 9/11: Shouldn&apos;t there be a cabinet-level IT department in the U.S. Government?&lt;/em&gt;

There should, but the present administration is so politically partisan they wouldn&apos;t allow it. Americans need security in times of threat. Halliburton doesn&apos;t. Bad for business.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669809</guid>
  	<pubDate>Thu, 13 May 2004 07:07:51 -0800</pubDate>
  	<dc:creator>zaelic</dc:creator>
</item>
<item>
  	<title>By: spazzm</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#669954</link>	
    <description>&lt;i&gt;&quot;[...] it seems like there&apos;s all kinds of efficiency, cost, and, especially, national security advantages to the governement using up-to-date, interoperable technology.&quot;&lt;/i&gt;

Which is precisely the reason they should &lt;i&gt;not&lt;/i&gt; have a cabinet-level IT department, of course.</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-669954</guid>
  	<pubDate>Thu, 13 May 2004 10:04:39 -0800</pubDate>
  	<dc:creator>spazzm</dc:creator>
</item>
<item>
  	<title>By: fluffycreature</title>
  	<link>http://www.metafilter.com/33065/Next-step-Xray-specs#670291</link>	
    <description>All I can say is version one of the software folks.  Attach it to a grid, cross reference a new dictionary as well, and voila, instant best-guess decryption.  Delicious!</description>
  	<guid isPermaLink="false">comment:www.metafilter.com,2008:site.33065-670291</guid>
  	<pubDate>Thu, 13 May 2004 18:20:52 -0800</pubDate>
  	<dc:creator>fluffycreature</dc:creator>
</item>

    </channel>
</rss>
