Home
last modified time | relevance | path

Searched refs:certificate (Results 1 – 25 of 27) sorted by relevance

12

/Linux-v5.15/certs/
DKconfig9 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
63 system keyring. Any certificate used for module signing is implicitly
71 bool "Reserve area for inserting a certificate without recompiling"
74 If set, space for an extra certificate will be reserved in the kernel
75 image. This allows introducing a trusted certificate to the default
79 int "Number of bytes to reserve for the extra certificate"
84 certificate to be inserted.
119 be checked to see if it matches such a certificate.
/Linux-v5.15/security/integrity/evm/
DKconfig59 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-v5.15/Documentation/crypto/
Dasymmetric-keys.rst108 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-v5.15/drivers/staging/greybus/
Dauthentication.c103 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()
Dgreybus_authentication.h56 __u8 certificate[CAP_CERTIFICATE_MAX_SIZE]; member
/Linux-v5.15/crypto/asymmetric_keys/
Dpkcs7.asn141 -- Certificates and certificate lists
46 certificate Certificate, -- X.509
DKconfig38 tristate "X.509 certificate parser"
45 public key packet found inside the certificate.
/Linux-v5.15/Documentation/process/
Dembargoed-hardware-issues.rst40 certificate. The list's PGP key and S/MIME certificate are available from
278 list's PGP key or with the list's S/MIME certificate. The mailing-list
280 subscriber with the subscriber's PGP key or S/MIME certificate. Details
289 the key and S/MIME certificate are conveyed to the subscribers by email
301 certificate. If a PGP key is used, it must be available from a public key
308 or the list's S/MIME certificate. The subscriber's email client can extract
309 the PGP key or the S/MIME certificate from the signature so the subscriber
Dchanges.rst126 Module signing and external certificate handling use the OpenSSL program and
/Linux-v5.15/include/linux/
Dkernel_read_file.h16 id(X509_CERTIFICATE, x509-certificate) \
/Linux-v5.15/security/integrity/ima/
DKconfig294 bool "Load X509 certificate onto the '.ima' trusted keyring"
301 .system keyring. This option enables X509 certificate
305 string "IMA X509 certificate path"
309 This option defines IMA X509 certificate path.
/Linux-v5.15/Documentation/kbuild/
Dreproducible-builds.rst85 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-v5.15/Documentation/maintainer/
Dmodifying-patches.rst9 rule (c) of the developers certificate of origin, you should ask the submitter
/Linux-v5.15/Documentation/admin-guide/
Dmodule-signing.rst103 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-v5.15/Documentation/virt/kvm/
Damd-memory-encryption.rst311 __u64 pdh_cert_uaddr; /* platform Diffie-Hellman certificate */
314 __u64 plat_certs_uaddr; /* platform certificate chain */
317 __u64 amd_certs_uaddr; /* AMD certificate */
/Linux-v5.15/Documentation/usb/
Dauthorization.rst91 Of course, this is lame, you'd want to do a real certificate
/Linux-v5.15/drivers/staging/greybus/Documentation/firmware/
Dfirmware-management261 __u8 certificate[CAP_CERTIFICATE_MAX_SIZE];
294 'cert_size' bytes of the 'certificate' shall be read by the user and others
/Linux-v5.15/net/wireless/certs/
Dsforshee.hex1 /* Seth Forshee's regdb certificate */
/Linux-v5.15/Documentation/dev-tools/
Dcheckpatch.rst526 …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-v5.15/Documentation/admin-guide/device-mapper/
Dverity.rst141 also gain new certificates at run time if they are signed by a certificate
/Linux-v5.15/Documentation/
DChanges126 Module signing and external certificate handling use the OpenSSL program and
/Linux-v5.15/include/linux/greybus/
Dgreybus_protocols.h348 __u8 certificate[]; member
/Linux-v5.15/Documentation/security/keys/
Dcore.rst913 One application of restricted keyrings is to verify X.509 certificate
914 chains or individual certificate signatures using the asymmetric key type.
/Linux-v5.15/Documentation/translations/it_IT/process/
Dmaintainer-pgp-guide.rst162 chiave principale attraverso firme certificate. È quindi importante
/Linux-v5.15/Documentation/filesystems/
Dfsverity.rst160 - ``ENOKEY``: the fs-verity keyring doesn't contain the certificate

12