Home
last modified time | relevance | path

Searched full:digitalsignature (Results 1 – 21 of 21) sorted by relevance

/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dcertificate.hpp19 DigitalSignature, enumerator
60 {KeyUsage::DigitalSignature, "DigitalSignature"},
/openbmc/openbmc/meta-security/meta-integrity/scripts/
H A Dima-gen-CA-signed.sh36 keyUsage=digitalSignature
37 #keyUsage = nonRepudiation, digitalSignature, keyEncipherment
/openbmc/bmcweb/test/http/
H A Dmutual_tls.cpp114 "digitalSignature, keyAgreement"); in TEST()
139 {"digitalSignature", "keyAgreement", "digitalSignature, keyAgreement"}) in TEST()
/openbmc/linux/certs/
H A Dsystem_keyring.c55 * restrict_link_by_digsig_builtin - Restrict digitalSignature key additions by the built-in keyring
63 * must have the digitalSignature usage field set.
107 * restrict_link_by_digsig_builtin_and_secondary - Restrict by digitalSignature.
115 * keyrings. The new key must have the digitalSignature usage field set.
H A Ddefault_x509.genkey15 keyUsage=digitalSignature
/openbmc/docs/security/
H A DTLS-configuration.md23 - `KeyUsage` contains required purpose `digitalSignature` and `keyAgreement`
76 keyUsage = digitalSignature, keyAgreement
103 keyUsage = digitalSignature, keyAgreement
112 keyUsage = digitalSignature, keyAgreement
/openbmc/linux/security/integrity/evm/
H A DKconfig68 key must have digitalSignature usage set.
/openbmc/linux/tools/testing/selftests/bpf/
H A Dverify_sig_setup.sh24 keyUsage=digitalSignature
/openbmc/linux/include/crypto/
H A Dpublic_key.h33 #define KEY_EFLAG_DIGITALSIG 1 /* set if the digitalSignature usage is set */
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/
H A DCertificate.interface.yaml41 DigitalSignature: The public key is used for verifying digital
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/CSR/
H A DCreate.interface.yaml106 DigitalSignature: The public key is used for verifying digital
/openbmc/linux/security/integrity/ima/
H A DKconfig256 digitalSignature usage set.
/openbmc/docs/designs/
H A Dredfish-tls-user-authentication.md208 - does KeyUsage contain required data ("digitalSignature" and "keyAgreement")
/openbmc/linux/crypto/asymmetric_keys/
H A Drestrict.c158 * Check if the new certificate has digitalSignature usage set. If it is,
H A Dx509_cert_parser.c593 * 0x80 is where digitalSignature lands in this bit string in x509_process_extension()
/openbmc/phosphor-certificate-manager/
H A Dcerts_manager.hpp156 * - DigitalSignature: The public key is used for verifying digital
H A Dcertificate.cpp62 {KU_DIGITAL_SIGNATURE, "DigitalSignature"},
/openbmc/bmcweb/src/
H A Dssl_key_handler.cpp328 addExt(x509, NID_key_usage, ("digitalSignature, keyEncipherment")); in generateSslCertificate()
/openbmc/qemu/tests/unit/
H A Dpkix_asn1_tab.c.inc32 {"digitalSignature", 1073741825, "0"},
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DCertificate_v1.xml166 <Member Name="DigitalSignature">
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DCertificate_v1.xml166 <Member Name="DigitalSignature">