From: "Peter Münster" <pmlists@free.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: permissions in luatex-cache
Date: Wed, 9 Jan 2008 23:36:14 +0100 [thread overview]
Message-ID: <20080109223614.GA30957@gaston.couberia.bzh> (raw)
In-Reply-To: <478540E4.3050802@wxs.nl>
On Wed, Jan 09, 2008 at 10:47:16PM +0100, Hans Hagen wrote:
>
> > And do these world writable directories present any security risk?
> > (For example: user A writes some evil code into file
> > $TEXMFCACHE/luatex-cache/context/XXX/fonts/otf/file.otf that makes user B
> > remove all his files when running "texexec --luatex document.tex")
>
> you can use a cache in your home path and make that country or city
> writable
So you mean, there is a security risk, luatex does not check its input and
arbitrary code can be executed?
The disadvantage of one cache per user is, that everybody needs to
regenerate the formats after an update, since the formats are also placed
there...
Cheers, Peter
(it was just a question out of curiosity, on my systems, there are no evil
users of course ;)
--
http://pmrb.free.fr/contact/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-09 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 20:41 Peter Münster
2008-01-09 21:47 ` Hans Hagen
2008-01-09 22:36 ` Peter Münster [this message]
2008-01-09 23:35 ` 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=20080109223614.GA30957@gaston.couberia.bzh \
--to=pmlists@free.fr \
--cc=ntg-context@ntg.nl \
/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).