From: Norbert Preining <preining@logic.at>
Cc: Mike Bird <mgb@yosemite.net>
Subject: Two problems with current ruby scripts
Date: Wed, 25 Oct 2006 10:19:06 +0200 [thread overview]
Message-ID: <20061025081906.GA13463@gamma.logic.tuwien.ac.at> (raw)
Dear all!
THe packages of ConTeXt I am currently preparing are tested by a user
and he send back the following questions/comments. Could you please
comment on this.
For the background: I install all the stubs from
scripts/context/stubs/unix
into /usr/bin, add a texmfstart stub that calls ruby with the right path
to texmfstart.rb.
----- Forwarded message from Mike Bird <mgb@yosemite.net> -----
> From: Mike Bird <mgb@yosemite.net>
> Subject: New texexec very confused
> To: debian-tex-maint@lists.debian.org
> Date: Tue, 24 Oct 2006 20:52:30 -0700
>
> The new ruby texexec is very confused. The problem of output
> defaulting to pdf instead of dvi has already been noted. Here
> are some additional problems:
>
> Command: texexec --output=dvips foo
> Should produce: foo.dvi
> Actually produces: foo.pdf
>
> Command: texexec --dvi foo
> Should produce: foo.dvi
> Actually produces: foo.dvi AND OVERWRITES foo.ps
>
> --Mike Bird
----- End forwarded message -----
----- Forwarded message from Mike Bird <mgb@yosemite.net> -----
> From: Mike Bird <mgb@yosemite.net>
> Subject: Is texmfstart secure?
> To: debian-tex-maint@lists.debian.org
> Date: Tue, 24 Oct 2006 21:08:53 -0700
>
> Package: context 2006.08.08-0.4
>
> If anyone who knows Ruby has time, can you tell if texmfstart is
> secure? I was really surprised to see client-server code. Even
> localhost services can lead to privilege escalation if not careful.
> For example, /usr/share/texmf/scripts/context/ruby/texmfstart.rb
> contains the following. I'm not a Ruby programmer but the comment
> leads me to think there is a potential problem here:
>
> # danger lurking
> buffer = ' ' * 260
> length = filemethod.call(filename,buffer,buffer.size)
> if length>0 then
> return buffer.slice(0..length-1)
>
> It looks like PRAGMA is trying to reinvent kpsewhich, integrate internet
> explorer, launch editors, and do a whole bunch of other stuff I haven't
> figured out. texexec should be a simple wrapper around tex or pdftex
> but it works via texmfstart.rb which is 2541 lines of Ruby - and that's
> a lot of Ruby. It may all be wonderful (I am not a Ruby programmer) but
> it makes me nervous.
>
> Is an older/simpler texexec still available?
>
> --Mike Bird
----- End forwarded message -----
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Università di Siena
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
TABLEY SUPERIOR (n.)
The look directed at you in a theatre bar in the interval by people
who've already got their drinks.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-tex-maint-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
next reply other threads:[~2006-10-25 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 8:19 Norbert Preining [this message]
2006-10-25 8:50 ` Hans Hagen
2006-10-25 13:27 ` Mojca Miklavec
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=20061025081906.GA13463@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=mgb@yosemite.net \
/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).