이 콘텐츠는 선택한 언어로 제공되지 않습니다.

17.2. Usage


ExtJoiner does not generate an extension in its MIME-64 encoded format; it joins existing MIME-64 encoded extensions. To join multiple custom extensions and add the extensions to a certificate request using ExtJoiner, do the following:
  1. Find and note the location of the extension program files.
  2. Run ExtJoiner, specifying the extension files. For example, if there are two extension files named myExt1 and myExt2 in a directory called /etc/extensions, then the command would be as follows:
    ExtJoiner /etc/extensions/myExt1 /etc/extensions/myExt2
    Copy to Clipboard Toggle word wrap
    This creates a base-64 encoded blob of the joined extensions, similar to this example:
    MEwwLgYDVR0lAQHBCQwIgYFKoNFBAMGClGC5EKDM5PeXzUGBi2CVyLNCQYFU
    iBakowGgYDVR0SBBMwEaQPMA0xCzAJBgNVBAYTAlVT
    Copy to Clipboard Toggle word wrap
  3. Copy the encoded blob, without any modifications, to a file.
  4. Verify that the extensions are joined correctly before adding them to a certificate request by converting the binary data to ASCII using the AtoB utility and then dumping the contents of the base-64 encoded blob using the dumpasn1 utility. For information on the AtoB utility, see Chapter 7, AtoB (Converting ASCII to Binary). The dumpasn1 tool can be downloaded at http://fedoraproject.org/extras/4/i386/repodata/repoview/dumpasn1-0-20050404-1.fc4.html.
    1. Run the AtoB utility to convert the ASCII to binary.
      AtoB  input_file output_file
      Copy to Clipboard Toggle word wrap
      where input_file is the path and file containing the base-64 encoded data in ASCII and output_file is the path and file for the utility to write the binary output.
    2. Run the dumpasn1 utility.
      dumpasn1output_file
      Copy to Clipboard Toggle word wrap
      where output_file is the path and file containing the binary data. The output looks 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 TRUE
    12 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.
    Copy to Clipboard Toggle word wrap
    If the output data do not appear to be correct, check that the original Java™ extension files are correct, and repeat converting the files from ASCII to binary and dumping the data until the correct output is returned.
  5. When the extensions have been verified, copy the base-64 encoded blob that was created by running ExtJoiner to the Certificate System wizard screen, and generate the certificate or the certificate signing request (CSR).
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat