www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra Bot (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-11118) Participation in Code Signing by HTTP Server project
Date Tue, 12 Jul 2016 07:45:21 GMT

     [ https://issues.apache.org/jira/browse/INFRA-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

#asfinfra Bot updated INFRA-11118:
----------------------------------
    Resolution: Unresolved
        Status: Pending Closed  (was: Waiting for user)

Hi, 

This issue has not been updated for at least 3 days, and is being marked as 'Pending Closed'.

  
In 5 days this issue will be automatically closed if no further updates are received. 


-- 
Cheers,
Apache Infrastructure Team

> Participation in Code Signing by HTTP Server project
> ----------------------------------------------------
>
>                 Key: INFRA-11118
>                 URL: https://issues.apache.org/jira/browse/INFRA-11118
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Codesigning
>            Reporter: William A. Rowe, Jr.
>            Assignee: Mark Thomas
>
> Raising a ticket to express interest...
> For some time, the value of an ASF shipping Windows httpd binary has been negligible,
as various lgpl and gpl components could be combined by other parties and assembled as a more
complete version of httpd.  It has been a few years since the httpd project has shipped Windows
binaries.
> With the introduction of code signing, this becomes interesting once again for httpd
to ship what are the official sources built for Windows, particularly with the introduction
of a persistent runtime in Visual C 14.  I'm willing to take this on if the Code signing service
agreement can be extended.
> Note that an httpd 2.4 package consists of about 48 programs and dynamic libraries, and
some 108 modules.  Internal to the installer there is a script rewriting binary and the install
package itself, for a total of soon to be 160 signed objects per release.  Releases of 2.4
occur about 4 times a year with releases of the legacy package (2.2 at present) which occur
2 times a year.
> Given the number of components, some batch submission mechanism is required to consider
this effort.
> Please provide feedback about the commitment to renewing the Symantec service, and I
would like to participate in this offering, going forwards, if the commitment is there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message