[texworks] HELP: Integrated Tw LaTeX2e Help dialogue

[Paul A Norman]

I am wondering if permission levels are helpful? Tainting?

Automatically allow a script to open/save anything that a user has
OKed  a Script dialogue for?

Then additionally allow scripts `seceretly' do things oked in a
prefereces dialogue.

With  Levels here?

 a) Sytem Wide, b) TexWorks directory tree, c) TeXWorks Config Tree,
d) TeXWorks Scripting Tree,

 Additionally options for? 1)  *TeX distribution whole tree 2) *TeX
distribution documentation tree

 Others ... ?

Do this in Preferences on a A) Genreic All scripts basis,

                                and   B) script by script basis?

If B)
flashing up the Script Manager if a script requests access to
somewehere not yet User approved?  Retain the answer - give options i)
This time, ii) always?

Start on a restrictive basis, and let the User free things up?
(assuming that Scripts can invoke the Script Manager permissions
dialougue as needed if the User tries to run an as yet un-Freed-up
script?

thoughts ...

Paul


On 1 July 2010 15:34, Alain Schremmer <schremmer.alain at gmail.com> wrote:
>
> 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
>