Netscape MANAGEMENT SYSTEM 4.5 - COMMAND-LINE Manual

Also see for NETSCAPE MANAGEMENT SYSTEM 4.5: Manual Manual Manual Installation and setup guide

Contents

Netscape MANAGEMENT SYSTEM 4.5 - COMMAND-LINE Manual Manual pdf 41 page image

UsageChapter 5 Extension Joiner Tool 413. Verify that the extensions are joined correctly before adding them to acertificate request. To do this, first you’ll need to convert the binary data toASCII format using the AtoB utility and then verify the binary data bydumping the contents of the base-64 encoded blob using the dumpasn1 utility.For information on the AtoB utility see, Chapter 7, “ASCII to Binary Tool” andfor the dumpasn1 utility see, Table 1-1 on page 15.Here’s how you would do this verification:a. Go to this directory: /bin/cert/toolsb. Enter this command: AtoB , substituting with the path to the file that contains the base-64 encodeddata in ASCII format (from Step 2) and with the path tothe file to write the base-64 encoded data in binary format.c. Next, enter this command: dumpasn1 , substituting with the path to the file to that contains the base-64encoded data in binary format. Your output should look similar to this:0 30 76: SEQUENCE {2 30 46: SEQUENCE {4 06 3: OBJECT IDENTIFIER extKeyUsage (2 5 29 37)9 01 1: BOOLEAN TRUE12 04 36: 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: }50 30 26: SEQUENCE {52 06 3: OBJECT IDENTIFIER issuerAltName (2 5 29 18)57 04 19: OCTET STRING: 30 11 A4 0F 30 0D 31 0B 30 09 06 03 55 04 06 13: 02 55 53: }: }0 warnings, 0 errors.d. If the output doesn’t appear right, repeat steps 1 through 3 to get thecorrect output.4. Copy the base-64 encoded blob in step 2 (the output generated by theExtJoiner) to the CMS wizard screen and generate the certificate or thecertificate signing request (CSR), if submitting the request to another CA.