<?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: PDF Security in SharePoint 2010</title>
	<atom:link href="http://blog.kiwibees.net/2011/04/06/pdf-security-in-sharepoint-2010/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kiwibees.net/2011/04/06/pdf-security-in-sharepoint-2010/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=pdf-security-in-sharepoint-2010</link>
	<description></description>
	<lastBuildDate>Thu, 11 Apr 2013 03:08:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: jbooker</title>
		<link>http://blog.kiwibees.net/2011/04/06/pdf-security-in-sharepoint-2010/#comment-5</link>
		<dc:creator>jbooker</dc:creator>
		<pubDate>Fri, 29 Jul 2011 12:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kiwibees.net/?p=55#comment-5</guid>
		<description><![CDATA[Julian,

I agree about security.  As you point out, adding inline MIME types is preferred.  That said, I do wonder how responsible it its (usability-wise) for MS not to have provided a secure viwer for O365.

I did this in response to the overwelming user demand and underwhelming MS response for a solution to open PDFs in the browser in O365.  In my opinion, MS should have provided a secure viewer before now.  Especially because they have a silverlight XPSPDF viewer already on docs.com.

I know some may feel differently, but to me, usability trumps the risk when it comes to pdfs in the browser.
Plus I will add for those who feel safe with the Browser File Handling set to strict, the fact that you can by-pass the &#039;&#039;noopen&#039;&#039; header like this proves it&#039;&#039;s really not so strict.

Thanks for looking,
Josh]]></description>
		<content:encoded><![CDATA[<p>Julian,</p>
<p>I agree about security.  As you point out, adding inline MIME types is preferred.  That said, I do wonder how responsible it its (usability-wise) for MS not to have provided a secure viwer for O365.</p>
<p>I did this in response to the overwelming user demand and underwhelming MS response for a solution to open PDFs in the browser in O365.  In my opinion, MS should have provided a secure viewer before now.  Especially because they have a silverlight XPSPDF viewer already on docs.com.</p>
<p>I know some may feel differently, but to me, usability trumps the risk when it comes to pdfs in the browser.<br />
Plus I will add for those who feel safe with the Browser File Handling set to strict, the fact that you can by-pass the &#8221;noopen&#8221; header like this proves it&#8221;s really not so strict.</p>
<p>Thanks for looking,<br />
Josh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian</title>
		<link>http://blog.kiwibees.net/2011/04/06/pdf-security-in-sharepoint-2010/#comment-4</link>
		<dc:creator>Julian</dc:creator>
		<pubDate>Thu, 28 Jul 2011 19:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kiwibees.net/?p=55#comment-4</guid>
		<description><![CDATA[Interesting workaround Josh. 
I do wonder how responsible (security-wise) it is to use javascript to work around an intentional security protection method though. 
In an on-premise situation you&#039;&#039;d be better off sticking with the &lt;em&gt;Inline Download Exclusion&lt;/em&gt; method, but in O365 you don&#039;&#039;t have that option yet, so your workaround would indeed be useful.

Rgds
JB]]></description>
		<content:encoded><![CDATA[<p>Interesting workaround Josh.<br />
I do wonder how responsible (security-wise) it is to use javascript to work around an intentional security protection method though.<br />
In an on-premise situation you&#8221;d be better off sticking with the <em>Inline Download Exclusion</em> method, but in O365 you don&#8221;t have that option yet, so your workaround would indeed be useful.</p>
<p>Rgds<br />
JB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbooker</title>
		<link>http://blog.kiwibees.net/2011/04/06/pdf-security-in-sharepoint-2010/#comment-3</link>
		<dc:creator>jbooker</dc:creator>
		<pubDate>Thu, 28 Jul 2011 14:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kiwibees.net/?p=55#comment-3</guid>
		<description><![CDATA[You can work around the Strict Browser File Handling by embeding the pdf in the page like this:

http://joshuabooker.com/Documents/pdf.aspx?file=browserfilehandling.pdf

The above is a PDF file in the browser from my Office365 site even though browser file handling is set to strict.

HTH,
Josh]]></description>
		<content:encoded><![CDATA[<p>You can work around the Strict Browser File Handling by embeding the pdf in the page like this:</p>
<p><a href="http://joshuabooker.com/Documents/pdf.aspx?file=browserfilehandling.pdf" rel="nofollow">http://joshuabooker.com/Documents/pdf.aspx?file=browserfilehandling.pdf</a></p>
<p>The above is a PDF file in the browser from my Office365 site even though browser file handling is set to strict.</p>
<p>HTH,<br />
Josh</p>
]]></content:encoded>
	</item>
</channel>
</rss>
