{
    "content": [
        {
            "type": "text",
            "text": "# OPENSSL-FORMAT-OPTIONS (info)\n\n## NAME\n\nopenssl-format-options - OpenSSL command input and output format options\n\n## SYNOPSIS\n\nopenssl command [ options ... ] [ parameters ... ]\n\n## DESCRIPTION\n\nSeveral OpenSSL commands can take input or generate output in a variety\nof formats.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS**\n- **COPYRIGHT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "OPENSSL-FORMAT-OPTIONS",
        "section": "",
        "mode": "info",
        "summary": "openssl-format-options - OpenSSL command input and output format options",
        "synopsis": "openssl command [ options ... ] [ parameters ... ]",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 14,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 85,
                "subsections": []
            },
            {
                "name": "COPYRIGHT",
                "lines": 8,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "openssl-format-options - OpenSSL command input and output format\noptions\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "openssl command [ options ... ] [ parameters ... ]\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Several OpenSSL commands can take input or generate output in a variety\nof formats.\n\nSince OpenSSL 3.0 keys, single certificates, and CRLs can be read from\nfiles in any of the DER, PEM or P12 formats. Specifying their input\nformat is no more needed and the openssl commands will automatically\ntry all the possible formats. However if the DER or PEM input format is\nspecified it will be enforced.\n\nIn order to access a key via an engine the input format ENGINE may be\nused; alternatively the key identifier in the <uri> argument of the\nrespective key option may be preceded by \"org.openssl.engine:\".  See\n\"Engine Options\" in openssl(1) for an example usage of the latter.\n",
                "subsections": []
            },
            "OPTIONS": {
                "content": "Format Options\nThe options to specify the format are as follows.  Refer to the\nindividual man page to see which options are accepted.\n\n-inform format, -outform format\nThe format of the input or output streams.\n\n-keyform format\nFormat of a private key input source.\n\n-CRLform format\nFormat of a CRL input source.\n\nFormat Option Arguments\nThe possible format arguments are described below.  Both uppercase and\nlowercase are accepted.\n\nThe list of acceptable format arguments, and the default, is described\nin each command documentation.\n\nDER A binary format, encoded or parsed according to Distinguished\nEncoding Rules (DER) of the ASN.1 data language.\n\nENGINE\nUsed to specify that the cryptographic material is in an OpenSSL\nengine.  An engine must be configured or specified using the\n-engine option.  A password or PIN may be supplied to the engine\nusing the -passin option.\n\nP12 A DER-encoded file containing a PKCS#12 object.  It might be\nnecessary to provide a decryption password to retrieve the private\nkey.\n\nPEM A text format defined in IETF RFC 1421 and IETF RFC 7468. Briefly,\nthis is a block of base-64 encoding (defined in IETF RFC 4648),\nwith specific lines used to mark the start and end:\n\nText before the BEGIN line is ignored.\n----- BEGIN object-type -----\nOT43gQKBgQC/2OHZoko6iRlNOAQ/tMVFNq7fL81GivoQ9F1U0Qr+DH3ZfaH8eIkX\nxT0ToMPJUzWAn8pZv0snA0um6SIgvkCuxO84OkANCVbttzXImIsL7pFzfcwV/ERK\nUM6j0ZuSMFOCr/lGPAoOQU0fskidGEHi1/kW+suSr28TqsyYZpwBDQ==\n----- END object-type -----\nText after the END line is also ignored\n\nThe object-type must match the type of object that is expected.\nFor example a \"BEGIN X509 CERTIFICATE\" will not match if the\ncommand is trying to read a private key. The types supported\ninclude:\n\nANY PRIVATE KEY\nCERTIFICATE\nCERTIFICATE REQUEST\nCMS\nDH PARAMETERS\nDSA PARAMETERS\nDSA PUBLIC KEY\nEC PARAMETERS\nEC PRIVATE KEY\nECDSA PUBLIC KEY\nENCRYPTED PRIVATE KEY\nPARAMETERS\nPKCS #7 SIGNED DATA\nPKCS7\nPRIVATE KEY\nPUBLIC KEY\nRSA PRIVATE KEY\nSSL SESSION PARAMETERS\nTRUSTED CERTIFICATE\nX509 CRL\nX9.42 DH PARAMETERS\n\nThe following legacy object-type's are also supported for\ncompatibility with earlier releases:\n\nDSA PRIVATE KEY\nNEW CERTIFICATE REQUEST\nRSA PUBLIC KEY\nX509 CERTIFICATE\n\nSMIME\nAn S/MIME object as described in IETF RFC 8551.  Earlier versions\nwere known as CMS and are compatible.  Note that the parsing is\nsimple and might fail to parse some legal data.\n",
                "subsections": []
            },
            "COPYRIGHT": {
                "content": "Copyright 2000-2021 The OpenSSL Project Authors. All Rights Reserved.\n\nLicensed under the Apache License 2.0 (the \"License\").  You may not use\nthis file except in compliance with the License.  You can obtain a copy\nin the file LICENSE in the source distribution or at\n<https://www.openssl.org/source/license.html>.\n\n3.0.2                             2026-06-02      OPENSSL-FORMAT-OPTIONS(1SSL)",
                "subsections": []
            }
        }
    }
}