9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dvips(1): RFC
Date: Fri, 20 Aug 2010 18:00:55 +0200	[thread overview]
Message-ID: <20100820160055.GA2014@polynum.com> (raw)
In-Reply-To: <13eff13d99b568358b119404df988f5d@hamnavoe.com>

On Fri, Aug 20, 2010 at 03:50:20PM +0100, Richard Miller wrote:
> > - There was support for embedded commands calling system(3).
>
> [...]
> The article also mentions some attacks on previewers, but the authors
> seem to have missed the potential exploits enabled by this "feature"
> of dvips.[...]

Proprietary (_bad!_) software hides the source. While some
"open" (_good!_) software shows you the hay stack... and invites you
to find the needle.

The current distributions of TeX and al. are so frightening, that it is
not surprising that the authors of the article have focused on
"features" documented and not tried to visit the Augean Stables.

And the fault is not on the original authors of the program, since the
state is unchanged in 15 or even 20 years! Only the amount of "goodies"
has increased.

In the same security audit for dvips(1), I will keep the automatic
generation of missing fonts, but the program/script called will be a
fully qualified name in the kerTeX hierarchy (supposed to be correctly
administrated), and not just a filename (last component)
called wherever such an executable with this name happen to exist in
the PATH.

The purpose of a---my claim---Unix purity that is Plan9 spirit TeX
distribution is that there is only a well identified, small amount
of added code to TeX and al. so that it can be audited, maintained
and used: no transfinite amount of hidden options.

Security will be the side-effect of maintenance and usability.

But I have been qualified by a former employer as a "psychorigid"
since I say (harshly) far more often: no! than yes, and remove more
easily than I add...  (starting by removing "great ideas" even
before starting to implement them...). So kerTeX will probably never be
very popular.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2010-08-20 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 11:02 tlaronde
2010-08-20 14:50 ` Richard Miller
2010-08-20 16:00   ` tlaronde [this message]
2010-08-20 15:42 ` Richard Miller
2010-08-20 16:03   ` tlaronde
2010-08-20 17:38     ` ron minnich
2010-08-20 21:13       ` tlaronde

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=20100820160055.GA2014@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.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).