[
https://issues.apache.org/jira/browse/DAEMON-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DAEMON-455.
--------------------------------
Resolution: Invalid
The signatures are valid. The expiry date of the certificate does not affect
the validity of the signature.
Further the prunmgr.exe and prunsrv.exe binaries from 1.3.3 are signed with the
exactly the same certificate.
> Windows executable prunsrv.exe has an expired certificate
> ---------------------------------------------------------
>
> Key: DAEMON-455
> URL: https://issues.apache.org/jira/browse/DAEMON-455
> Project: Commons Daemon
> Issue Type: Bug
> Components: prunsrv
> Affects Versions: 1.3.3
> Environment: Windows server
> Reporter: Kristin Murphy
> Priority: Major
> Labels: certificate, prunsrv
> Fix For: 1.3.4
>
> Attachments: prunsrv-expired-certificate.png
>
>
> The Windows executable file named prunsrv.exe has an expired certificate as
> seen in the attached image. The certificate was valid from 1/13/2022 to
> 1/14/2023. One thing I noticed is that the Windows executable file named
> prunmgr.exe has a certificate that is valid from 9/30/2022 to 11/21/2033. If
> possible it would be great to use the same certificate, or set the expiry of
> the one in prunsrv.exe to be 10 years out as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
