Category:OWASP OpenSign Server Project - Revision history

Kait Disney-Leugers at 19:50, 23 January 2014

2014-01-23T19:50:29Z

2014-01-23T18:27:58Z

2014-01-23T01:57:52Z

2009-02-25T09:15:27Z

‎Code Signing and Verification

2009-02-25T09:14:49Z

‎Code Signing and Verification

2009-02-25T09:14:28Z

‎Code Signing

2009-02-25T09:00:06Z

‎User Documentation

2009-02-25T08:42:30Z

‎Client Usage

2009-02-25T08:38:03Z

‎Client Usage

2009-02-25T08:37:04Z

‎Client Usage

@@ Line 4: / Line 4: @@
 ! width="500" align="center" | <br>
 |-
-| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/Category:OWASP_Project]]
+| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]
 | align="right" |

@@ Line 1: / Line 1: @@
-[[Image:OWASP Inactive Banner.jpg|1155px]]
+{|
 {{:Project Information:template OpenSign Server Project}}
 [[Category:OWASP Project]]

← Older revision		Revision as of 01:57, 23 January 2014
Line 1:		Line 1:
		+	[[Image:OWASP Inactive Banner.jpg\|1155px]]
	{{:Project Information:template OpenSign Server Project}}		{{:Project Information:template OpenSign Server Project}}
	[[Category:OWASP Project]]		[[Category:OWASP Project]]

@@ Line 101: / Line 101: @@
 . Generation of a certificate sign request (CSR)
-. Processing the (CSR) by making use of the web-interface or the client application. Either way a certificate is returned on success. Furthermore, a copy of the certificate is stored within the server-infrastructure.
+. Processing the CSR by making use of the web-interface or the client application. Either way a certificate is returned on success. Furthermore, a copy of the certificate is stored within the server-infrastructure.
 .Signing the code module by making use of the previously generated key.

@@ Line 93: / Line 93: @@
 ==Code Signing and Verification==
-This section describes the steps required for code-signing and verification support by the OpenSign infrastructure.
+This section describes the steps required for code-signing and verification supported by the OpenSign infrastructure.
 '''Signing'''

← Older revision		Revision as of 09:14, 25 February 2009
Line 91:		Line 91:


−	==Code Signing==	+	==Code Signing and Verification==
		+
		+	This section describes the steps required for code-signing and verification support by the OpenSign infrastructure.
		+
		+	'''Signing'''
		+
		+	1. Local generation of the private code-signing key. The key should be stored in a password-protected keystore.
		+
		+	2. Generation of a certificate sign request (CSR)
		+
		+	3. Processing the (CSR) by making use of the web-interface or the client application. Either way a certificate is returned on success. Furthermore, a copy of the certificate is stored within the server-infrastructure.
		+
		+	4.Signing the code module by making use of the previously generated key.
		+
		+	'''Verification'''
		+
		+	1. Downloading the certificate by browsing the OpenSign X.509 hierarchy online or by use of the client application, which is the recommended option.
		+
		+	2. Importing the certificate as a trusted certificate in the local key-store.
		+
		+	3. Verifying the signed code module by use of the public key embedded in the downloaded certificate.

	=Releases=		=Releases=

@@ Line 63: / Line 63: @@
 This command processes a certificate sign request. The request is sent to the server, which takes the login credentials and checks if the user is approved to have a OpenSign certificate and if so a certificate is generated and sent to the user in return.
-==Setting up the X.509 Hierarchy==
+==Steps for setting up the X.509 Hierarchy==
 ==Code Signing==

@@ Line 47: / Line 47: @@
     java -jar OSSJClient-[version].jar [command]
-Executing the client application without the command-parameter, will print a list of all possible commands to the console. All commands take mandatory and optional parameter, which are also depicted by entering a command without any parameter.
+Executing the client application without the command-parameter, will print a list of all possible commands to the console. All commands take mandatory and optional parameter, which are also depicted by calling a command without any parameter.
 The possible commands are:
@@ Line 53: / Line 53: @@
 '''verifycert'''
-This command takes a certificate and verifies it by downloading the certificate chain from the server and verifying all certificates. A detailed transcript is printed to the console.
+This command takes a certificate file and verifies it. Additionally, the application downloads and verifies the certificate chain. A detailed transcript is printed to the console.
 '''getcert'''

@@ Line 43: / Line 43: @@
 ==Client Usage==
-Open a console and brows into folder OSSJClient-1.0. The usage of the command line client is as follows.
+Open a console and brows into folder OSSJClient-1.0. To start the client enter following command:
     java -jar OSSJClient-[version].jar [command]