Bug#316154: [tex-live] Re: Bug#316154: texmf.cfg: Close possible security problem

2005-08-27 Thread Hilmar Preusse
On 21.08.05 Karl Berry ([EMAIL PROTECTED]) wrote: Hi Karl, % The default settings are not secure when you process LaTeX files of % possibly doubtful origin. In this case, set openin_any = p. I'm not too excited about putting such a vague and alarmist message into texmf.cnf. I have

Bug#316154: [tex-live] Re: Bug#316154: texmf.cfg: Close possible security problem

2005-08-27 Thread Karl Berry
Well, the submitter spoke about some mal code sent to somebody, who calls it and the LaTeX file does something really bad. As far as I know, foreign files can't do anything *really* bad. As distributed, TeX will only write files (via \openout) under TEXMFOUTPUT (if set) or the current

Bug#316154: [tex-live] Re: Bug#316154: texmf.cfg: Close possible security problem

2005-08-27 Thread Hans Hagen Outside
Hilmar Preusse wrote: Well, the submitter spoke about some mal code sent to somebody, who calls it and the LaTeX file does something really bad. I don't know how realistic that scenario is. Well, normally I don't read very long documnents before processing them since one can open a file

Bug#316154: [tex-live] Re: Bug#316154: texmf.cfg: Close possible security problem

2005-08-21 Thread Karl Berry
Hi Hilmar, % The default settings are not secure when you process LaTeX files of % possibly doubtful origin. In this case, set openin_any = p. I'm not too excited about putting such a vague and alarmist message into texmf.cnf. I have no objection to putting in something more specific,

Bug#316154: [tex-live] Re: Bug#316154: texmf.cfg: Close possible security problem

2005-06-29 Thread Hans Hagen
Frank Küster wrote: Dear Thomas, dear TeXLive people, in Debian bug report we have been asked to change the setting of openin_any in texmf.cnf: Joachim Breitner [EMAIL PROTECTED] wrote: the shipped /etc/texmf/texmf.cfg has the following lines: openout_any = p openin_any = a While the