| /linux-6.12.1/certs/ |
| D | Kconfig | 9 Provide the file name of a private key/certificate in PEM format,
11 the URI should identify, both the certificate and its corresponding
16 certificate as described in Documentation/admin-guide/module-signing.rst
64 system keyring. Any certificate used for module signing is implicitly
72 bool "Reserve area for inserting a certificate without recompiling"
75 If set, space for an extra certificate will be reserved in the kernel
76 image. This allows introducing a trusted certificate to the default
80 int "Number of bytes to reserve for the extra certificate"
85 certificate to be inserted.
137 be checked to see if it matches such a certificate.
[all …]
|
| /linux-6.12.1/security/integrity/evm/ |
| D | Kconfig | 60 bool "Load an X509 certificate onto the '.evm' trusted keyring"
64 Load an X509 certificate onto the '.evm' trusted keyring.
66 This option enables X509 certificate loading from the kernel
72 string "EVM X509 certificate path"
76 This option defines X509 certificate path.
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-class-firmware-attributes | 269 certificate, signature, save_signature:
270 These attributes are used for certificate based authentication. This is
279 Installing a certificate to enable feature::
282 echo "signed certificate" > authentication/Admin/certificate
284 Updating the installed certificate::
287 echo "signed certificate" > authentication/Admin/certificate
289 Removing the installed certificate::
292 echo "" > authentication/Admin/certificate
300 You cannot enable certificate authentication if a supervisor password
302 Clearing the certificate results in no bios-admin authentication method
[all …]
|
| D | sysfs-driver-intel_sdsi | 77 (RO) Used to read back the current meter certificate for the CPU
78 from Intel On Demand hardware. The meter certificate contains
87 (RO) Used to read back the current state certificate for the CPU
88 from On Demand hardware. The state certificate contains
|
| /linux-6.12.1/Documentation/crypto/ |
| D | asymmetric-keys.rst | 108 PGP-specific metadata, whereas X.509 has arbitrary certificate identifiers.
372 This allows for verification of certificate chains by adding each
373 certificate in order (starting closest to the root) to a keyring. For
376 certificate chain to be validated::
383 # Create and restrict a keyring for the certificate chain
387 # Attempt to add each certificate in the chain, starting with the
388 # certificate closest to the root.
393 If the final end-entity certificate is successfully added to the "chain"
398 restricting the keyring after linking the root certificate::
400 # Create a keyring for the certificate chain and add the root
[all …]
|
| /linux-6.12.1/drivers/staging/greybus/ |
| D | authentication.c | 106 u8 *certificate, u32 *size, u8 *result) in cap_get_ims_certificate() argument
136 memcpy(certificate, response->certificate, *size); in cap_get_ims_certificate()
233 ims_cert->certificate, in cap_ioctl()
|
| D | greybus_authentication.h | 55 __u8 certificate[CAP_CERTIFICATE_MAX_SIZE]; member
|
| /linux-6.12.1/crypto/asymmetric_keys/ |
| D | pkcs7.asn1 | 48 -- Certificates and certificate lists
53 certificate Certificate, -- X.509
|
| D | Kconfig | 27 tristate "X.509 certificate parser"
34 public key packet found inside the certificate.
|
| /linux-6.12.1/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 40 certificate. The list's PGP key and S/MIME certificate are available from
324 list's PGP key or with the list's S/MIME certificate. The mailing list
326 subscriber with the subscriber's PGP key or S/MIME certificate. Details
335 specific mailing lists, the key and S/MIME certificate are conveyed to the
348 certificate. If a PGP key is used, it must be available from a public key
355 or the list's S/MIME certificate. The subscriber's email client can extract
356 the PGP key or the S/MIME certificate from the signature so the subscriber
|
| /linux-6.12.1/include/linux/ |
| D | kernel_read_file.h | 16 id(X509_CERTIFICATE, x509-certificate) \
|
| /linux-6.12.1/Documentation/virt/coco/ |
| D | sev-guest.rst | 130 related to the additional certificate data that is returned with the report.
131 The certificate data returned is being provided by the hypervisor through the
138 and snp_ext_report_req.certs_address will contain the certificate blob. If the
142 See GHCB specification for further detail on how to parse the certificate blob.
|
| /linux-6.12.1/security/integrity/ima/ |
| D | Kconfig | 276 bool "Load X509 certificate onto the '.ima' trusted keyring"
283 .system keyring. This option enables X509 certificate
287 string "IMA X509 certificate path"
291 This option defines IMA X509 certificate path.
|
| /linux-6.12.1/Documentation/security/tpm/ |
| D | tpm-security.rst | 101 endorsement certificate, creating an attestation identity key and
160 Curve version of the certificate exists at 01C00002, but will work
161 equally well with the RSA certificate (at 01C00001).
165 of the generated primary key against the one in the certificate (the
170 certificate itself must be verified to chain back to the manufacturer
|
| /linux-6.12.1/Documentation/networking/ |
| D | tls-handshake.rst | 84 Authentication material such as x.509 certificates, private certificate
93 keys containing an x.509 certificate and the private key for that
94 certificate. Then, it invokes this function:
|
| /linux-6.12.1/drivers/accel/habanalabs/common/ |
| D | habanalabs_ioctl.c | 711 memcpy(&info->certificate, &sec_attest_info->certificate, sizeof(info->certificate)); in sec_attest_info()
758 memcpy(&info->certificate, &dev_info_signed->certificate, sizeof(info->certificate)); in dev_info_signed()
|
| /linux-6.12.1/Documentation/kbuild/ |
| D | reproducible-builds.rst | 85 1. Generate a persistent signing key. Add the certificate for the key
89 signing key's certificate, set ``CONFIG_MODULE_SIG_KEY`` to an
|
| /linux-6.12.1/include/linux/habanalabs/ |
| D | cpucp_if.h | 1369 __u8 certificate[SEC_CERTIFICATE_BUF_SZ]; member
1394 __u8 certificate[SEC_CERTIFICATE_BUF_SZ]; member
|
| /linux-6.12.1/Documentation/maintainer/ |
| D | modifying-patches.rst | 9 rule (c) of the developers certificate of origin, you should ask the submitter
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | module-signing.rst | 104 and its corresponding X.509 certificate in PEM form, or — on systems where
107 certificate and a private key.
179 in the ``CONFIG_MODULE_SIG_KEY`` option, and the certificate and key therein will
|
| /linux-6.12.1/arch/arm/boot/dts/marvell/ |
| D | kirkwood-c200-v1.dts | 201 label = "certificate";
|
| D | armada-370-c200-v2.dts | 259 label = "certificate";
|
| /linux-6.12.1/drivers/staging/greybus/Documentation/firmware/ |
| D | firmware-management | 261 __u8 certificate[CAP_CERTIFICATE_MAX_SIZE];
294 'cert_size' bytes of the 'certificate' shall be read by the user and others
|
| /linux-6.12.1/Documentation/usb/ |
| D | authorization.rst | 88 Of course, this is lame, you'd want to do a real certificate
|
| /linux-6.12.1/include/uapi/drm/ |
| D | habanalabs_accel.h | 1291 __u8 certificate[SEC_CERTIFICATE_BUF_SZ]; member
1314 __u8 certificate[SEC_CERTIFICATE_BUF_SZ]; member
|