public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Julien Dutant <julien.dutant-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Lua filter security: safe mode?
Date: Tue, 10 May 2022 06:45:05 -0700 (PDT)	[thread overview]
Message-ID: <13cd1f3a-bc26-49cf-a7df-ec8d56fcf05an@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 941 bytes --]

Hi all,

As discussed a while ago on 
https://github.com/pandoc/lua-filters/issues/207#issuecomment-1067959808 
and said in Pandoc's manual, running Lua filters downloaded from internet 
is a security risk as Pandoc is run with full privileges. 

But doesn't all the risk only comes for Lua's `os` module (and perhaps 
io?), which few filters actually use? If so, would it be possible for 
Pandoc to run Lua filters without this module, providing an alternative 
flag (something like --lua-filter-safe) to run a filter safely?

J

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/13cd1f3a-bc26-49cf-a7df-ec8d56fcf05an%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1297 bytes --]

             reply	other threads:[~2022-05-10 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 13:45 Julien Dutant [this message]
     [not found] ` <13cd1f3a-bc26-49cf-a7df-ec8d56fcf05an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-12 12:16   ` Albert Krewinkel
     [not found]     ` <87r14yzzb1.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-05-12 13:15       ` Albert Krewinkel

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=13cd1f3a-bc26-49cf-a7df-ec8d56fcf05an@googlegroups.com \
    --to=julien.dutant-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@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).