Netscape MANAGEMENT SYSTEM 6.0 - COMMAND-LINE Manual page 41

Verify that the extensions are joined correctly before adding them to a
3.
certificate request. To do this, first you'll need to convert the binary data to
ASCII format using the
dumping the contents of the base-64 encoded blob using the
For information on the
for the
dumpasn1
Here's how you would do this verification:
Go to this directory:
a.
Enter this command:
b.
<input_file>
data in ASCII format (from Step 2) and
the file to write the base-64 encoded data in binary format.
Next, enter this command:
c.
<output_file>
encoded data in binary format. Your output should look similar to this:
0 30 76: SEQUENCE {
2 30 46:
4 06 3:
9 01 1:
12 04 36:
:
:
:
:
50 30 26:
52 06 3:
57 04 19:
:
:
:
:
0 warnings, 0 errors.
If the output doesn't appear right, repeat steps 1 through 3 to get the
d.
correct output.
Copy the base-64 encoded blob in step 2 (the output generated by the
4.
ExtJoiner) to the CMS wizard screen and generate the certificate or the
certificate signing request (CSR), if submitting the request to another CA.
utility and then verify the binary data by
AtoB
utility see, Chapter 7, "ASCII to Binary Tool" and
AtoB
utility see, Table 1-1 on page 15.
<server_root>/bin/cert/tools
AtoB <input_file> <output_file>
with the path to the file that contains the base-64 encoded
dumpasn1 <ouput_file>
with the path to the file to that contains the base-64
SEQUENCE {
OBJECT IDENTIFIER extKeyUsage (2 5 29 37)
BOOLEAN TRUE
OCTET STRING
30 22 06 05 2A 83 45 04 03 06 0A 51 82 E4 42 83
33 93 DE 5F 35 06 06 2D 82 57 22 CD 09 06 05 51
38 81 6A 4A
}
SEQUENCE {
OBJECT IDENTIFIER issuerAltName (2 5 29 18)
OCTET STRING
30 11 A4 0F 30 0D 31 0B 30 09 06 03 55 04 06 13
02 55 53
}
}
dumpasn1
, substituting
with the path to
<output_file>
, substituting
Chapter 5 Extension Joiner Tool
Usage
utility.
41