linux-kernel - Re: [PATCH] docs: Makefile: Add -no-shell-escape option to LATEXOPTS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e7ce363c-c154-50b7-016f-0f98bf13a0b9@gmail.com>
Date:   Thu, 10 Feb 2022 10:43:34 +0900
From:   Akira Yokosawa <akiyks@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH] docs: Makefile: Add -no-shell-escape option to LATEXOPTS

On Thu, 10 Feb 2022 10:26:53 +0900,
Akira Yokosawa wrote:
> By adding this option, message of "restricted \write18 enabled" from
> LaTeX can be silenced.
> 
> As there is no use of \write18 in LaTeX sources from sphinx-build, it
> is safe to add this option.

Jon,
JFYI, there is a ticket on the message at:

    https://tex.stackexchange.com/questions/76105/what-does-restricted-write18-enabled-mean-and-why-does-texlive-keep-reporting

I think David Carlisle's answer covers most of your concerns.

        Thanks, Akira 

> 
> Reported-by: Jonathan Corbet <corbet@....net>
> Signed-off-by: Akira Yokosawa <akiyks@...il.com>
> ---
[...]