Project Information:template OpenSign Server Project - Final Review - Second Reviewer - F

Project Deliveries & Objectives

OWASP OpenSign Server Project's Deliveries & Objectives

1. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please exemplify writing down those of them that haven't been realised.

At this point the core functionality of the OpenSign project has been developed and tested. This includes the issuing and verifying of certificates within a client server infrastructure. Users must be authenticated and approved by an issuer to use the issuing-service. The issuing is done easily by making use of the client application or online via a web-form. However, OpenSign is not an independent solution for code signing yet. It relies on java-keytool (or an application with the same intention) to generate the client side keys and the certificate sign requests. There is no graphical interface for the client in place. Also the support of .NET code signing was not taken into account yet.

OK

2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage.

OpenSign Server: 80%

OK

Client Tools – OSSJClient: 90%

OK

Documentation: 30%

OK

3. Please do use the right hand side column to provide advice and make work suggestions.

Second comments:

• I was able to get this running fine on MS OS with Java/Maven and compile in the Eclipse IDE
• it would be nice it it would be possible to simply download and run the code

for the server and the client - AGREE

• available user documentation: what can I do with each tool, how (for instance under the form of a '5 minutes introduction' and reference list of available functions) ? - AGREE
• I would like to see the C# version as well
• it would be nice if the 'trunk' would be documented in a way that let the user know:
• how to run the server and clients (a global 'readme' file is missing).
• The 'opensign-design' documentation could be completed.

Assessment Criteria

OWASP Project Assessment Criteria

1. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Alpha Quality status?

2. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Beta Quality status?

• Include user documentation in Project's OWASP Wiki page(s)

OK

3. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Release Quality status?

• Include online documention built into tool (based on required user documentation)
• Be run through Fortify Software's open source review (if appropriate) and FindBugs

OK

4. Please do use the right hand side column to provide advice and make work suggestions.