[
https://issues.apache.org/jira/browse/TIKA-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692508#comment-16692508
]
Luis Filipe Nassif commented on TIKA-2785:
------------------------------------------
Hi [[email protected]], just to confirm ForkParser is not vulnerable to this
because it loads parsers after redirecting stdout/stdin, right?
> Switch parent/child IPC to mmap file from stdout/stderr in tika-server
> ----------------------------------------------------------------------
>
> Key: TIKA-2785
> URL: https://issues.apache.org/jira/browse/TIKA-2785
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0, 1.20
>
>
> When I added {{-spawnChild}} to tika-server, I followed the pattern in
> ForkParser of redirecting stdout/stderr for the parent to listen to output
> from the child process. This relies on the parsers not grabbing a pointer to
> stdout/stderr _before_ we redirect it. However, it is possible for parsers
> to grab stdout/stderr during static initialization, as happens with log4j
> configured to write to stdout/stderr.
> This means that the communication channel from child to parent is unreliable.
> Let's switch child to parent communication in {{-spawnChild}} to a shared
> mmap'd file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
