[jira] [Commented] (INFRA-3991) Request for code signing certificate

["Mark Thomas (JIRA)" <ji...@apache.org>]

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

Mark Thomas commented on INFRA-3991:
------------------------------------

We now have an NDA in place with Symantec and they have provided some documentation on the service. The next steps are for use to review this documentation. After that, Symantec will arrange a "deep-dive" WebEx where we can explore the details of how this would work.

The documentation is in the private foundation repo under Correspondence/Symantec

If anyone doesn't have access to that area, ping me directly and I'll send you the files.

I'd like to get at least one representative from Logging, OpenOffice, Tomcat and Infra to review these docs and to attend the WebEx. I'm happy to cover Tomcat and Infra although the more the merrier. I'll add my review notes shortly.

> Request for code signing certificate
> ------------------------------------
>
>                 Key: INFRA-3991
>                 URL: https://issues.apache.org/jira/browse/INFRA-3991
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>            Reporter: Scott Deboy
>            Assignee: Mark Thomas
>
> The Logging Services project provides a WebStart-deployed Swing application, Chainsaw.  To deploy Chainsaw via WebStart and take advantage of all of its features, the jars that are downloaded must be signed by a code signing certificate which has been signed by a trusted root CA.
> It would seem to me it would make sense to have this code signing certificate and associated keys managed by the ASF and not be a project-specific certificate, so other projects could take advantage of the same resources.  If you feel it makes more sense to get Logging Services its own code signing certificate that is managed by the PMC, I'm fine with that as well - I would just like the issue to be resolved.
> I assume if this resource were an ASF-wide resource, the keys and certificate would be managed by infra.  If so, I'm not sure what workflow infra would like to use - maybe a jira issue with release candidate jars and pgp info, and signed jars could be added back to the same jira?  We don't release often, so just let us know what you would like.
> Our needs are relatively simple, and I understand others may have more complex needs.  PMC members or the RM could manage self-signed certificates and 'get by', but I would rather have an official code signing cert provided by ASF itself.



--
This message was sent by Atlassian JIRA
(v6.1#6144)