<?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: Security researcher argues for built-in PDF viewer in Windows</title>
	<atom:link href="http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/</link>
	<description>PDF News, PDF Articles, PDF Tips and PDF Rants on ... PDF!</description>
	<lastBuildDate>Sat, 14 May 2011 22:40:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Nick De Roeck</title>
		<link>http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/comment-page-1/#comment-2952</link>
		<dc:creator>Nick De Roeck</dc:creator>
		<pubDate>Thu, 13 May 2010 09:43:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.4xpdf.com/?p=4012#comment-2952</guid>
		<description>The mess I&#039;m referring too is the leaky abstraction that Adobe has created around the concept &#039;document&#039; with PDF.

PDF contains Javascript (and actions), so one has to assume that a PDF can contain it. It doesn&#039;t matter if this only a small part of the spec.

From a security standpoint receiving a PDF is becoming equivalent to receiving an application - which is a big difference. Relaying on the goodness of a &#039;well behaving client app&#039; isn&#039;t also that great.

The Google solution is a good one, albeit an ironic one.
It keeps the document outside, and turns the PDF back into a &#039;safe&#039; static document that displays in your browser.</description>
		<content:encoded><![CDATA[<p>The mess I&#8217;m referring too is the leaky abstraction that Adobe has created around the concept &#8216;document&#8217; with PDF.</p>
<p>PDF contains Javascript (and actions), so one has to assume that a PDF can contain it. It doesn&#8217;t matter if this only a small part of the spec.</p>
<p>From a security standpoint receiving a PDF is becoming equivalent to receiving an application &#8211; which is a big difference. Relaying on the goodness of a &#8216;well behaving client app&#8217; isn&#8217;t also that great.</p>
<p>The Google solution is a good one, albeit an ironic one.<br />
It keeps the document outside, and turns the PDF back into a &#8216;safe&#8217; static document that displays in your browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Hanna</title>
		<link>http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/comment-page-1/#comment-2950</link>
		<dc:creator>Rowan Hanna</dc:creator>
		<pubDate>Wed, 12 May 2010 15:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.4xpdf.com/?p=4012#comment-2950</guid>
		<description>That&#039;s a great point -- I rarely download a PDF that I receive via email before I have viewed it in Gmail&#039;s PDF viewer. It much quicker to open the PDF via Gmail instead of downloading it and then waiting for a PDF viewer to launch.

This would help skip over the security issue as well. If Gmail can hvae a PDF viewer, why can&#039;t Windows??</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great point &#8212; I rarely download a PDF that I receive via email before I have viewed it in Gmail&#8217;s PDF viewer. It much quicker to open the PDF via Gmail instead of downloading it and then waiting for a PDF viewer to launch.</p>
<p>This would help skip over the security issue as well. If Gmail can hvae a PDF viewer, why can&#8217;t Windows??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl De Abrew</title>
		<link>http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/comment-page-1/#comment-2946</link>
		<dc:creator>Karl De Abrew</dc:creator>
		<pubDate>Tue, 11 May 2010 07:54:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.4xpdf.com/?p=4012#comment-2946</guid>
		<description>Actually -- exhibit A in this case would be the built-in Gmail PDF viewer -- I almost never download a PDF file within gmail when I&#039;m looking for a quick read/heads up....</description>
		<content:encoded><![CDATA[<p>Actually &#8212; exhibit A in this case would be the built-in Gmail PDF viewer &#8212; I almost never download a PDF file within gmail when I&#8217;m looking for a quick read/heads up&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Hanna</title>
		<link>http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/comment-page-1/#comment-2945</link>
		<dc:creator>Rowan Hanna</dc:creator>
		<pubDate>Tue, 11 May 2010 07:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.4xpdf.com/?p=4012#comment-2945</guid>
		<description>Why does Windows include an application that lets you preview JPG, BMP, TIFF, PNG, etc, images? 

PDF is just as ubiquitous as TIFF files (and other image formats) these days and yet if you want to view them on Windows, you have to download a separate app. Whereas on Mac OSX and a lot of Linux distros, a basic built-in PDF viewer is included by default.

With regards to the security exploit, there is no &quot;mess&quot; that needs to be cleaned up. Simply put, there are countless ways that security exploits can make it onto your computer. Using your definition of a &quot;mess&quot; you could argue against using USB drives, floppy disks or even the Internet because all of these mediums can be used to transport security exploits onto your computer.

JavaScript is just one small feature of PDF and is mostly irrelevant to the majority of users -- they won&#039;t even notice if they&#039;re using a PDF viewer that doesn&#039;t support it.

Getting back to Sullivan&#039;s point, if you use a PDF viewer on your computer that does not support JavaScript (or allows you to work without JavaScript support enabled), then there is no security exploit. The same thing can&#039;t be said for removing the possibility of exploits from other Windows applications, such as Microsoft Word.

If Microsoft were to introduce a basic PDF viewer for Windows (similar to the Preview feature in Mac OSX) then it would be a win-win situation for Windows users. They would no longer need to download a separate app and they wouldn&#039;t be exposed to this security exploit.</description>
		<content:encoded><![CDATA[<p>Why does Windows include an application that lets you preview JPG, BMP, TIFF, PNG, etc, images? </p>
<p>PDF is just as ubiquitous as TIFF files (and other image formats) these days and yet if you want to view them on Windows, you have to download a separate app. Whereas on Mac OSX and a lot of Linux distros, a basic built-in PDF viewer is included by default.</p>
<p>With regards to the security exploit, there is no &#8220;mess&#8221; that needs to be cleaned up. Simply put, there are countless ways that security exploits can make it onto your computer. Using your definition of a &#8220;mess&#8221; you could argue against using USB drives, floppy disks or even the Internet because all of these mediums can be used to transport security exploits onto your computer.</p>
<p>JavaScript is just one small feature of PDF and is mostly irrelevant to the majority of users &#8212; they won&#8217;t even notice if they&#8217;re using a PDF viewer that doesn&#8217;t support it.</p>
<p>Getting back to Sullivan&#8217;s point, if you use a PDF viewer on your computer that does not support JavaScript (or allows you to work without JavaScript support enabled), then there is no security exploit. The same thing can&#8217;t be said for removing the possibility of exploits from other Windows applications, such as Microsoft Word.</p>
<p>If Microsoft were to introduce a basic PDF viewer for Windows (similar to the Preview feature in Mac OSX) then it would be a win-win situation for Windows users. They would no longer need to download a separate app and they wouldn&#8217;t be exposed to this security exploit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick De Roeck</title>
		<link>http://www.4xpdf.com/2010/05/security-researcher-argues-for-built-in-pdf-viewer-in-windows/comment-page-1/#comment-2944</link>
		<dc:creator>Nick De Roeck</dc:creator>
		<pubDate>Tue, 11 May 2010 07:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.4xpdf.com/?p=4012#comment-2944</guid>
		<description>Sean Sullivan argues that this viewer can also be a separate download, but why not download Adobe Reader then?

Isn&#039;t this asking Microsoft to fix the mess Adobe made with PDF?
And in one go, opening yet another front for Microsoft where they will need to defend against accusations of being the big bad gorilla crushing innovation?

Apple&#039;s PDF viewer is indeed an incredibly useful application, but it&#039;s not like they are getting a lot of big gratitude from Adobe, if you&#039;re following the Adobe evangelists, they take every opportunity to take a stab at Apple&#039;s app.

Fact of the matter is: PDF is broken. Becoming a jack of all trades, master at none.</description>
		<content:encoded><![CDATA[<p>Sean Sullivan argues that this viewer can also be a separate download, but why not download Adobe Reader then?</p>
<p>Isn&#8217;t this asking Microsoft to fix the mess Adobe made with PDF?<br />
And in one go, opening yet another front for Microsoft where they will need to defend against accusations of being the big bad gorilla crushing innovation?</p>
<p>Apple&#8217;s PDF viewer is indeed an incredibly useful application, but it&#8217;s not like they are getting a lot of big gratitude from Adobe, if you&#8217;re following the Adobe evangelists, they take every opportunity to take a stab at Apple&#8217;s app.</p>
<p>Fact of the matter is: PDF is broken. Becoming a jack of all trades, master at none.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

