Project Information:template OpenSign Server Project - Final Review - First Reviewer - D

From OWASP
Revision as of 02:32, 27 October 2008 by Philipp Potisk (Talk | contribs)

Jump to: navigation, search

Clik here to return to the previous page.

FINAL REVIEW
PART I

Project Deliveries & Objectives

OWASP OpenSign Server Project's Deliveries & Objectives

QUESTIONS ANSWERS

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.

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%

Client Tools – OSSJClient: 90%

Documentation: 30%

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

First comments:

  • it would be nice it it would be possible to simply download and run the code

for the server and the client (I have made some tests under linux, this seems not to be the case for the latter releases available on the project web page)

  • available scripts for starting both under MS win & linux, with default config
  • 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) ?
  • is the C# code available for download and execution ?
  • it would be nice if the 'trunk' would be documented in a way that let the user know:

- how to compile everything (without needing to install libraries from the web) ?

- how to run the server and clients (a global 'readme' file is missing).

  • Moreover, the 'opensign-design' document could be completed.


PART II

Assessment Criteria

OWASP Project Assessment Criteria

QUESTIONS ANSWERS

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?

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

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