/openbmc/openbmc/poky/meta/recipes-support/ca-certificates/ca-certificates/ |
H A D | 0002-update-ca-certificates-use-SYSROOT.patch | 36 PEM="$ETCCERTSDIR/$(basename "$CERT" .crt | sed -e 's/ /_/g' \ 39 - if ! test -e "$PEM" || [ "$(readlink "$PEM")" != "$CERT" ] 40 + if ! test -e "$PEM" || [ "$(readlink "$PEM")" != "${CERT##$SYSROOT}" ] 42 - ln -sf "$CERT" "$PEM" 43 + ln -sf "${CERT##$SYSROOT}" "$PEM" 44 echo "+$PEM" >> "$ADDED"
|
H A D | 0003-update-ca-certificates-use-relative-symlinks-from-ET.patch | 60 PEM="$ETCCERTSDIR/$(basename "$CERT" .crt | sed -e 's/ /_/g' \ 63 - if ! test -e "$PEM" || [ "$(readlink "$PEM")" != "${CERT##$SYSROOT}" ] 65 + if ! test -e "$PEM" || [ "$(readlink "$PEM")" != "${DST}" ] 67 - ln -sf "${CERT##$SYSROOT}" "$PEM" 68 + ln -sf "${DST}" "$PEM" 69 echo "+$PEM" >> "$ADDED"
|
/openbmc/docs/designs/management-console/ |
H A D | Authorities_List_Management.md | 19 2. It only extracts the first certificate given a PEM encoded file with multiple 20 certs; however, Google's trust bundle file contains multiple PEM encoded 28 1. Bulk Installation: given a PEM file with multiple root certificates, it 31 2. Bulk Replacement: given a PEM file with multiple root certificates, it will 55 corresponding object in DBus, dump individual certificates into PEM files in the 57 boost's `ssl_context`) for each certificate, and finally copy the PEM file to 58 the installation path(the PEM file will have a fixed name) 68 PEM file. 71 invocation, it deletes all current authority objects, takes the input PEM, and 80 It only extracts the first certificate even if the PEM contains multiple root
|
/openbmc/linux/tools/certs/ |
H A D | print-cert-tbs-hash.sh | 35 if ! PEM="$(openssl x509 -inform DER -in "${CERT}" 2>/dev/null || openssl x509 -in "${CERT}")"; then 56 RANGE_AND_DIGEST=($(echo "${PEM}" | \ 87 echo "${PEM}" | \
|
/openbmc/bmcweb/redfish-core/include/generated/enums/ |
H A D | certificate.hpp | 12 PEM, enumerator 53 {CertificateType::PEM, "PEM"},
|
/openbmc/bmcweb/scripts/ |
H A D | generate_auth_certificates.py | 384 encoding=serialization.Encoding.PEM 409 encoding=serialization.Encoding.PEM, 414 encoding=serialization.Encoding.PEM 436 encoding=serialization.Encoding.PEM, 445 encoding=serialization.Encoding.PEM
|
/openbmc/qemu/scripts/ |
H A D | u2f-setup-gen.py | 68 privkey_pem = privkey.private_bytes(encoding=Encoding.PEM, 71 pubkey_pem = pubkey.public_bytes(encoding=Encoding.PEM,
|
/openbmc/openbmc/meta-openembedded/meta-oe/classes/ |
H A D | signing.bbclass | 140 # Import a certificate *chain* from a PEM file to a role. 169 # Import a certificate from PEM file to a role. To be used 192 # Import a public key from PEM file to a role. To be used with SoftHSM. 220 # Import a private key from PEM file to a role. To be used with SoftHSM. 239 # Import a private and public key from PEM file to a role. To be used
|
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libmozilla/ |
H A D | libmozilla-ca-perl_20240924.bb | 1 SUMMARY = "Mozilla's CA cert bundle in PEM format"
|
/openbmc/linux/certs/ |
H A D | Kconfig | 9 Provide the file name of a private key/certificate in PEM format, 60 If set, this option should be the filename of a PEM-formatted file 127 If set, this option should be the filename of a PEM-formatted file
|
H A D | Makefile | 50 -outform PEM -out $@ -keyout $@ $(keytype-y) 2>&1
|
/openbmc/linux/tools/testing/selftests/bpf/ |
H A D | verify_sig_setup.sh | 43 -outform PEM -out ${tmp_dir}/signing_key.pem \
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | module-signing.rst | 103 and its corresponding X.509 certificate in PEM form, or — on systems where 108 If the PEM file containing the private key is encrypted, or if the 116 This option can be set to the filename of a PEM-encoded file containing 170 -config x509.genkey -outform PEM -out kernel_key.pem \ 192 trusted certificates can be provided in a PEM-encoded file referenced by the
|
/openbmc/openbmc-tools/openbmctool/ |
H A D | README.md | 103 File: The [PEM](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail) file 112 File: The PEM file containing both certificate and private key. 120 File: The PEM file containing only certificate.
|
/openbmc/linux/Documentation/hwmon/ |
H A D | lineage-pem.rst | 38 Example: the following will load the driver for a Lineage PEM at address 0x40
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/freeradius/files/ |
H A D | 0013-raddb-certs-Makefile-fix-the-occasional-verification.patch | 55 - $(OPENSSL) x509 -inform PEM -outform DER -in ca.pem -out ca.der 56 + @[ -f ca.der ] || $(OPENSSL) x509 -inform PEM -outform DER -in ca.pem -out ca.der
|
/openbmc/linux/Documentation/security/ |
H A D | digsig.rst | 83 Keys can be in PEM or converted to the kernel format.
|
/openbmc/openbmc/poky/meta/recipes-support/ca-certificates/ |
H A D | ca-certificates_20241223.bb | 2 DESCRIPTION = "This package includes PEM files of CA certificates to allow \
|
/openbmc/docs/designs/ |
H A D | redfish-tls-user-authentication.md | 112 "CertificateType": "PEM" 128 "CertificateType": "PEM"
|
H A D | certificate-revocation-list.md | 59 interface to be `CRLString`, which contains the PEM encoded CRL. We can add more
|
/openbmc/qemu/docs/system/ |
H A D | tls.rst | 14 provided in PEM format. Aside from the core fields, the certificates 236 When copying the PEM files to the target host, save them twice, once as 266 used for a network client or server, and determines which PEM files are
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/vpnc/vpnc/ |
H A D | long-help | 155 filename and path to the CA-PEM-File
|
/openbmc/openbmc-test-automation/redfish/dmtf_tools/ |
H A D | test_redfishtool_certificate.robot | 144 ... CertificateType=PEM CertificateUri=${certificate_dict} 399 ... CertificateType=PEM CertificateUri=${certificate_dict}
|
/openbmc/openbmc-test-automation/docs/ |
H A D | certificate_generate.md | 134 "CertificateType": "PEM",
|
/openbmc/docs/security/ |
H A D | TLS-configuration.md | 345 "CertificateType": "PEM" 385 "CertificateType": "PEM"
|