<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx</link><description>You might have recently heard something about the new "Microsoft Office Isolated Conversion Environment", a tool we are providing to help protect Office 2003 users from malicious content in Office files. You might be asking yourself what it is, and why</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2492478</link><pubDate>Wed, 09 May 2007 04:47:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2492478</guid><dc:creator>Foolhardy</dc:creator><description>&lt;P&gt;&amp;gt;&amp;gt;A somewhat neglected feature that's been in Windows since Windows 2000 is job objects...&lt;/P&gt;
&lt;P&gt;I really wish there was a better user interface to these features. The official UI methods that I know of are: a server resource management program (I forget the name), which I presume uses jobs, the "Run this program with restricted access" option of Run As makes a basic restricted token, the similar option of Process Explorer, and the Untrusted, Basic User and Restricted SAFER levels use, which use restricted tokens, with job objects to mitigate desktop attacks.&lt;/P&gt;
&lt;P&gt;Still, it'd be nice to have a command line scriptable or otherwise automated interface with fine grained control over groups and job limits built into the OS. I ended up creating my own command line app, ulimitnt (see post URL), to utilize restricted tokens, jobs and desktop objects effectively.&lt;/P&gt;
&lt;P&gt;It's a shame too... restricted tokens are very powerful: it's even possible to build an application rights (as a subset of the user's rights) framework with some planning.&lt;/P&gt;
&lt;P&gt;[dcl] I agree - most of this is left over from an early sandboxing project, but one problem is that a lot of stuff breaks, and it's a support call waiting to happen if you do use it on regular apps. You really need to build an app to run in an environment like this. Stay tuned - once you see the details, you'll see the complexity.&lt;/P&gt;
&lt;P&gt;That said, I've been tossing around the idea of making a toolkit so that people could use all this more easily. No promises, but I've had thoughts much along the same lines as your comments.&lt;/P&gt;</description></item><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2528617</link><pubDate>Thu, 10 May 2007 22:33:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2528617</guid><dc:creator>Russ Cooper</dc:creator><description>&lt;P&gt;About time you got around to writing this David!! I can't wait to plug it into email gateways to replace MIME decoders with something better than magic byte detection capabilities! Please find a way for us to put this into a managed sink on Exchange!&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Russ&lt;/P&gt;</description></item><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2548629</link><pubDate>Fri, 11 May 2007 18:50:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2548629</guid><dc:creator>Ryan Russell</dc:creator><description>&lt;P&gt;Hm, app proxy for file formats, huh?&lt;/P&gt;
&lt;P&gt;Is there a page somewhere that would tell one how to configure the jail mode, if one wanted to see what could be done from there, independent of MOICE?&lt;/P&gt;
&lt;P&gt;[dcl] It isn't configurable, so it would be a very short page. There is one thing you could do to further tweak it on Vista, which would be to add some deny all firewall rules for the converters. I would have liked to have that in there, but we wanted to get it out for people to use, and you could do that with a VB script if you liked.&lt;/P&gt;
&lt;P&gt;You wouldn't want to tighten the screws any further - they're already screwed down as tight as they can get without breaking things - we went overboard, then backed off just enough for things to run, and had to fix a couple of things in the apps for it to work.&lt;/P&gt;
&lt;P&gt;I will be documenting everything we've done, and might even wrap this into a library you could use for your own apps, though don't hold your breath - I'm really busy. It will probably eventually happen, but I can't commit to even a vague schedule. &lt;/P&gt;</description></item><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2557859</link><pubDate>Sat, 12 May 2007 04:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2557859</guid><dc:creator>Justin Polazzo</dc:creator><description>&lt;P&gt;What about people who do not run office 2007?&lt;/P&gt;
&lt;P&gt;Are you saying the 2003/2000 versions of office will still be able to read these converted-but-still-associated-with-older-version docs?&lt;/P&gt;
&lt;P&gt;-JP&lt;/P&gt;
&lt;P&gt;[dcl] That's the point - the converter pack allows downlevel versions of Office to read the new file format. So the file starts out in what was originally the native format for Office 2003, gets converted to the new format (and likely sanitized in the process), and you can then use the converter to allow Office 2003 to read it in.&lt;/P&gt;</description></item><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2558513</link><pubDate>Sat, 12 May 2007 04:44:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2558513</guid><dc:creator>Justin Polazzo</dc:creator><description>&lt;P&gt;sorry, the 2003 should have been removed from that question....&lt;/P&gt;
&lt;P&gt;I have a lot of friends at colleges that could use this, but also still have office 2000 running.&lt;/P&gt;
&lt;P&gt;would this work for them as well?&lt;/P&gt;
&lt;P&gt;-JP&lt;/P&gt;
&lt;P&gt;[dcl] Office 2000, or Office XP? Support for the converter pack is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN&gt;
&lt;DIV class=downloadInfo&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;B&gt;Supported Operating Systems: &lt;/B&gt;Windows 2000 Service Pack 4; Windows Server 2003; Windows XP Service Pack 1&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;B&gt;Recommended Microsoft Office programs:&lt;/B&gt;&lt;BR&gt;
&lt;UL&gt;
&lt;LI&gt;Microsoft Word 2000 with Service Pack 3, Microsoft Excel 2000 with Service Pack 3, and Microsoft PowerPoint 2000 with Service Pack 3 &lt;BR&gt;
&lt;LI&gt;Microsoft Word 2002 with Service Pack 3, Microsoft Excel 2002 with Service Pack 3, and Microsoft PowerPoint 2002 with Service Pack 3&lt;BR&gt;
&lt;LI&gt;Microsoft Office Word 2003 with at least Service Pack 1, Microsoft Office Excel 2003 with at least Service Pack 1, and Microsoft Office PowerPoint 2003 with at least Service Pack 1 &lt;BR&gt;
&lt;LI&gt;Microsoft Office Word Viewer 2003&lt;BR&gt;
&lt;LI&gt;Microsoft Office Excel Viewer 2003&lt;BR&gt;
&lt;LI&gt;Microsoft Office PowerPoint Viewer 2003&lt;BR&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;I'm not 100% sure what MOICE supports in terms of the full deal with file blocking and so on - that may be only Office 2003, but I can check on Monday. However, it can be used as a command-line tool to convert files to the new format, and they'll do so in a protected manner. You can then open them with anything the converter pack supports (above). As far as the sandbox goes, I know it is tested on XP and up, not as sure about Windows 2000, and Win9x doesn't support what it needs at all - no security on Win9x.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/SPAN&gt;</description></item><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2579784</link><pubDate>Sun, 13 May 2007 00:29:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2579784</guid><dc:creator>alexeck</dc:creator><description>&lt;P&gt;Very interesting post. One question: How will one deal with current O27 files? You're not going to "downconvert" and then upconvert those, are you? You're just upconverting the older files? &lt;/P&gt;
&lt;P&gt;[dcl] exactly&lt;/P&gt;
&lt;P&gt;in other words, this doesn't do anything to protect user's from a Metro file which is exploited, right?&lt;/P&gt;
&lt;P&gt;[dcl] - right - this wouldn't protect from a native Office 2007 file that is exploitable. It wouldn't convert, and in the second place, if the converter itself could be made to run completely arbitrary code, it could emit any file it likes in the new format. If that file were an exploitable 2007 file, then you'd have an exploit. This is exactly why I said customers would be _safer_ - it's still possible something could get through, but a lot of things will get blocked - there are whole classes of attacks that can't make the transition.&lt;/P&gt;</description></item><item><title>Microsoft Office Isolated Conversion Environment</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2650785</link><pubDate>Tue, 15 May 2007 17:56:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2650785</guid><dc:creator>Teamzille.de</dc:creator><description>&lt;p&gt;Bei der Entwicklung von Office 2007 ist den Entwicklern aufgefallen, dass in alten Office-Dokumenten enthaltener Schadcode verloren geht, wenn diese in das neue Format konvertiert werden. Genaugenommen passiert dies nicht immer aber die Wahrscheinlichkei&lt;/p&gt;
</description></item><item><title>re: New File Converter Coming Soon</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#2790514</link><pubDate>Tue, 22 May 2007 14:22:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2790514</guid><dc:creator>Nathanael Jones</dc:creator><description>&lt;P&gt;Will this help with word 2.0 files in an way? We've still got thousands of Word 2.0 files, and newer versions of Word don't open them correctly. Word 2.0 won't run on newer computers, so we're going to be stuck when our last pentium 3 dies.&lt;/P&gt;
&lt;P&gt;[dcl] I don't know - it's basically the same code as Office 2007 would use to convert the files, so it would do the same job. If you've got lots of files, my assumption would be that most (all?) of them aren't malicious, and MOICE may be overkill. I believe Word 2 will run on a recent system - saw one of our devs run it on his Win2k3 system one day. You can also certainly install all this into a virtual PC running whatever combination of downlevel OS and Office you like. You don't need actual hardware.&lt;/P&gt;
&lt;P&gt;Given the security implications of the older parsing code, it isn't a great idea to expect us to support older formats forever.&amp;nbsp;Taking into account&amp;nbsp;the engineering cost of bringing that code up to current standards and the decreasing user base, something has to give. What might be a good idea for you would be to use whatever version of Office you feel has good fidelity (though we do strive to make this work really well - I'll accept your word in terms of how it works for you), and upconvert the files to something newer - Word 2 was great 15 years ago...&lt;/P&gt;
&lt;P&gt;Hope this helps - and this is all just IMHO, and not an official statement on behalf of Office.&lt;/P&gt;</description></item><item><title>Microsoft Office Isolated Conversion Environment</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#5240329</link><pubDate>Tue, 02 Oct 2007 12:37:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5240329</guid><dc:creator>IT, IS, etc... </dc:creator><description>&lt;p&gt;Как всегда: начинаешь копать одно, а выясняешь для себя много нового совсем из другой оперы. Сегодня...&lt;/p&gt;
</description></item><item><title>Microsoft Office Isolated Conversion Environment</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#5590268</link><pubDate>Mon, 22 Oct 2007 06:50:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5590268</guid><dc:creator>ИТ, ИБ и т.п.</dc:creator><description>&lt;p&gt;Как всегда: начинаешь копать одно, а выясняешь для себя много нового совсем из другой оперы. Сегодня...&lt;/p&gt;
</description></item><item><title>Ooops, formatele vechi nu sunt secure?</title><link>http://blogs.msdn.com/david_leblanc/archive/2007/05/08/new-file-converter-coming-soon.aspx#6994206</link><pubDate>Sat, 05 Jan 2008 20:36:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6994206</guid><dc:creator>Weblogul lui Zoli</dc:creator><description>&lt;p&gt;Nu. Totusi, Office 2003 SP3 blocheaza o serie de formate de documente (foarte putin folosite in Microsoft&lt;/p&gt;
</description></item></channel></rss>