## Re: [MiKTeX] 2.8 update breaks \include

 Re: [MiKTeX] 2.8 update breaks \include From: David Allsopp - 2010-04-25 08:53:41 ```Christian Schenk wrote: > On 24.04.2010 18:48, Evan Cooch wrote: > > I just upgraded my 2.8 install, and now am completely unable to > > compile any file that uses \include to include individual subfiles (in > > my case, individual chapters of a large book). When I try to compile, > > I now get an error message that looks like > > > > !I can't write > > on file `../chapter5/chapter5.aux'. > > > > \@include ...\immediate \openout \@partaux #1.aux > > > > Please type another output name: > > This is a side-effect of a change I made last week: relative and > absolute path names are no longer allowed when using the \openout > directive. > > This article (to be published next week) was the trigger for the bug > fix: > http://www.usenix.org/event/leet10/tech/techAbstracts.html#Checkoway > > You can get the old (unsafe) behavior by setting this environment > variable: > > set MIKTEX_ALLOWUNSAFEOUTPUTFILES=1 Wouldn't a command line option to TeX be a good idea as well (not that you can't just set that variable locally in a command prompt before running). Presumably the -include-directory option to TeX still allows *parent* paths without issue? Later posts seem to suggest that it's absolute and parent-relative paths that are prohibited (which is good). > The bug fix was applied to the 2.7 binaries too. > > Think I should publish publish this on the issues page. Has this latest update also addressed the security vulnerability in \write18 which I reported at the end of December? David ```