# [texworks] HELP: Integrated Tw LaTeX2e Help dialogue

Alain Schremmer schremmer.alain at gmail.com
Thu Jul 1 05:34:50 CEST 2010

On Jun 30, 2010, at 10:25 PM, Paul A Norman wrote:
>
> To me it means that yes there are dangers and problems, but if we, as
> you suggest, work hard looking for necessary safguards, then we should
> not fear the lion -- but be as bold as one in what we do!
>
> On 1 July 2010 12:39, Reinhard Kotucha <reinhard.kotucha at web.de>
> wrote:
>> On 1 July 2010 Paul A Norman wrote:
>>
>> If such a script is able to create/overwrite a file called ~/.rhosts
>> I'm quite concerned.  The world is not as friendly as had been
>> 20~years ago.
>>
>> It would be nice if the level of paranoia can be defined in
>> texmf.cnf .
>>
>> Example:
>>
>>  > % Allow TeX \openin, \openout, or \input on filenames starting
>> with `.'
>>  > % (e.g., .rhosts) or outside the current tree (e.g., /etc/passwd)?
>>  > % a (any)        : any file can be opened.
>>  > % r (restricted) : disallow opening "dotfiles".
>>  > % p (paranoid)   : as `r' and disallow going to parent
>> directories, and
>>  > %                  restrict absolute paths to be under
>> \$TEXMFOUTPUT.
>>  > openout_any = p
>>  > openin_any = a

Not entirely sure what the Example means. But I am all for leaving
the responsibility to the user via a setting in what is called on the
Mac "preferences"

Regards
--schremmer