Searched refs:certificate (Results 1 – 25 of 33) sorted by relevance
12
| /linux-5.19.10/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
62 system keyring. Any certificate used for module signing is implicitly
70 bool "Reserve area for inserting a certificate without recompiling"
73 If set, space for an extra certificate will be reserved in the kernel
74 image. This allows introducing a trusted certificate to the default
78 int "Number of bytes to reserve for the extra certificate"
83 certificate to be inserted.
121 be checked to see if it matches such a certificate.
[all …]
|
| /linux-5.19.10/security/integrity/evm/ |
| D | Kconfig | 59 bool "Load an X509 certificate onto the '.evm' trusted keyring"
63 Load an X509 certificate onto the '.evm' trusted keyring.
65 This option enables X509 certificate loading from the kernel
70 string "EVM X509 certificate path"
74 This option defines X509 certificate path.
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-class-firmware-attributes | 249 certificate, signature, save_signature:
250 These attributes are used for certificate based authentication. This is
259 Installing a certificate to enable feature::
262 echo "signed certificate" > authentication/Admin/certificate
264 Updating the installed certificate::
267 echo "signed certificate" > authentication/Admin/certificate
269 Removing the installed certificate::
272 echo "" > authentication/Admin/certificate
280 You cannot enable certificate authentication if a supervisor password
282 Clearing the certificate results in no bios-admin authentication method
[all …]
|
| /linux-5.19.10/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-5.19.10/drivers/staging/greybus/ |
| D | authentication.c | 103 u8 *certificate, u32 *size, u8 *result) in cap_get_ims_certificate() argument
133 memcpy(certificate, response->certificate, *size); in cap_get_ims_certificate()
230 ims_cert->certificate, in cap_ioctl()
|
| D | greybus_authentication.h | 56 __u8 certificate[CAP_CERTIFICATE_MAX_SIZE]; member
|
| /linux-5.19.10/crypto/asymmetric_keys/ |
| D | pkcs7.asn1 | 41 -- Certificates and certificate lists
46 certificate Certificate, -- X.509
|
| D | Kconfig | 26 tristate "X.509 certificate parser"
33 public key packet found inside the certificate.
|
| /linux-5.19.10/Documentation/virt/coco/ |
| D | sev-guest.rst | 107 related to the additional certificate data that is returned with the report.
108 The certificate data returned is being provided by the hypervisor through the
115 and snp_ext_report_req.certs_address will contain the certificate blob. If the
119 See GHCB specification for further detail on how to parse the certificate blob.
|
| /linux-5.19.10/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 40 certificate. The list's PGP key and S/MIME certificate are available from
279 list's PGP key or with the list's S/MIME certificate. The mailing-list
281 subscriber with the subscriber's PGP key or S/MIME certificate. Details
290 the key and S/MIME certificate are conveyed to the subscribers by email
302 certificate. If a PGP key is used, it must be available from a public key
309 or the list's S/MIME certificate. The subscriber's email client can extract
310 the PGP key or the S/MIME certificate from the signature so the subscriber
|
| D | changes.rst | 145 Module signing and external certificate handling use the OpenSSL program and
|
| /linux-5.19.10/include/linux/ |
| D | kernel_read_file.h | 16 id(X509_CERTIFICATE, x509-certificate) \
|
| /linux-5.19.10/security/integrity/ima/ |
| D | Kconfig | 292 bool "Load X509 certificate onto the '.ima' trusted keyring"
299 .system keyring. This option enables X509 certificate
303 string "IMA X509 certificate path"
307 This option defines IMA X509 certificate path.
|
| /linux-5.19.10/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-5.19.10/Documentation/maintainer/ |
| D | modifying-patches.rst | 9 rule (c) of the developers certificate of origin, you should ask the submitter
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | module-signing.rst | 103 and its corresponding X.509 certificate in PEM form, or — on systems where
106 certificate and a private key.
174 in the ``CONFIG_MODULE_SIG_KEY`` option, and the certificate and key therein will
|
| /linux-5.19.10/Documentation/virt/kvm/x86/ |
| D | amd-memory-encryption.rst | 319 __u64 pdh_cert_uaddr; /* platform Diffie-Hellman certificate */
322 __u64 plat_certs_uaddr; /* platform certificate chain */
325 __u64 amd_certs_uaddr; /* AMD certificate */
|
| /linux-5.19.10/arch/arm/boot/dts/ |
| D | kirkwood-c200-v1.dts | 201 label = "certificate";
|
| D | armada-370-c200-v2.dts | 259 label = "certificate";
|
| /linux-5.19.10/Documentation/usb/ |
| D | authorization.rst | 91 Of course, this is lame, you'd want to do a real certificate
|
| /linux-5.19.10/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-5.19.10/net/wireless/certs/ |
| D | sforshee.hex | 1 /* Seth Forshee's regdb certificate */
|
| /linux-5.19.10/drivers/platform/x86/intel/ |
| D | Kconfig | 166 certificate and capability license.
|
| /linux-5.19.10/Documentation/dev-tools/ |
| D | checkpatch.rst | 526 …ww.kernel.org/doc/html/latest/process/submitting-patches.html#developer-s-certificate-of-origin-1-1
571 line should be added according to Developer's certificate of
574 …oc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
583 …oc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
|
| /linux-5.19.10/Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 141 also gain new certificates at run time if they are signed by a certificate
|
12