You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Konstantin Kolinko (Jira)" <ji...@apache.org> on 2022/12/08 00:44:00 UTC

[jira] [Comment Edited] (DAEMON-429) prunsrv.exe, and prunmgr.exe improper binary protection

    [ https://issues.apache.org/jira/browse/DAEMON-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644558#comment-17644558 ] 

Konstantin Kolinko edited comment on DAEMON-429 at 12/8/22 12:43 AM:
---------------------------------------------------------------------

I do not know how OP does it, but
StackOverflow mentions, that such value can be created by manually editing the registry, https://stackoverflow.com/a/38851495


was (Author: kkolinko):
I do not know how OP does it, but
StackOverflow mentions, that such value can be created by manually editing the registry,

> prunsrv.exe, and prunmgr.exe improper binary protection
> -------------------------------------------------------
>
>                 Key: DAEMON-429
>                 URL: https://issues.apache.org/jira/browse/DAEMON-429
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun, prunsrv
>    Affects Versions: 1.2.3
>            Reporter: Sambasivarao Garidi
>            Priority: Critical
>
> The PESecurity utility identified the specified (prunsrv.exe, and prunmgr.exe) does not have Control Flow Guard enabled causing it to fail our software security check. We would like to request that these (prunsrv.exe, and prunmgr.exe) to be compiled with the Control Flow Guard enabled in the next Apache commons-daemon release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)