ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl-Zrdc6muVEXhFdZ2Pf3w6Nw@public.gmane.org>
Subject: Shell escape & ConTeXt (was: Re: EPS to PDF--en masse?)
Date: Tue, 8 Jun 2004 16:52:10 +0100	[thread overview]
Message-ID: <20040608165210.6918@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <83201.89697-yNUTs0qEFpZ/1wmUHrjjoYdd74u8MsAO@public.gmane.org>

TeX on Mac OS X Mailing List said this at Mon, 7 Jun 2004 20:00:01 -0400:

>Shell escape is a mechanism which basically stops TeX processing, allows
>an external program (like epstopd script) to run and then resume the
>processing. The problem is that it allows any program to be run. So if
>someone sends you a malicious TeX file, it can do good amount of damage
>like wipe your home folder.

Hi MacOSX-TeXers and ConTeXters.

I just happened to revisit this recently, wondering how to make the
gwTeX/ConTeXt experience a bit more usable "out of the box". I remember a
few months ago some ConTeXters suggesting on MacOSX-TeX that shell_escape
be set to true, to make things easier for users. The security
implications quashed that idea pretty quickly.

Instead, how about if gwTeX's default texmf.tetex/context/config/
texexec.ini includes the line:

  for  tetex  set  TeXPassString     to  -progname=context -shell-escape

That ought to be as safe as any ConTeXt installation, without negatively
impacting risk for other macro packages, right?

(disclaimer: I don't run gwTeX on my main rig (TeXLive for me), but I try
to keep an eye on what's going on over there. For whatever TeXLive-ish
reason, my texexec.ini includes  --default-translate-file=cp8bit on that
line as well.)
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay                      atl-Zrdc6muVEXhFdZ2Pf3w6Nw@public.gmane.org
 Computing Dept, Lancaster University   +44(0)1524/594.537
 Lancaster, LA1 4YR, UK             Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


       reply	other threads:[~2004-06-08 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83201.89697@email.esm.psu.edu>
     [not found] ` <83201.89697-yNUTs0qEFpZ/1wmUHrjjoYdd74u8MsAO@public.gmane.org>
2004-06-08 15:52   ` Adam Lindsay [this message]
2004-06-08 19:32     ` Shell escape & ConTeXt Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040608165210.6918@mail.comp.lancs.ac.uk \
    --to=atl-zrdc6muvexhfdz2pf3w6nw@public.gmane.org \
    --cc=MacOSX-TeX-yNUTs0qEFpZ/1wmUHrjjoYdd74u8MsAO@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).