Searched refs:certificates (Results 1 – 20 of 20) sorted by relevance
| /linux/certs/ |
| H A D | Kconfig | 96 containing trusted X.509 certificates to be included in the default 133 If set, only certificates signed by keys on the builtin trusted 164 bool "Provide system-wide ring of revocation certificates" 168 If set, this allows revocation certificates to be stored in the 173 string "X.509 certificates to be preloaded into the system blacklist keyring" 177 containing X.509 certificates to be included in the default blacklist
|
| /linux/net/wireless/ |
| H A D | Kconfig | 22 # may need to update this when certificates are changed and are 105 which certificates are part of the kernel sources 116 certificates like in the kernel sources (net/wireless/certs/) 120 for your certificates, and if cfg80211 is built-in they also must be.
|
| /linux/arch/s390/include/asm/ |
| H A D | ipl.h | 119 struct list_head certificates; member
|
| /linux/crypto/asymmetric_keys/ |
| H A D | pkcs7.asn1 | 19 certificates CHOICE {
|
| /linux/Documentation/admin-guide/ |
| H A D | module-signing.rst | 29 This facility uses X.509 ITU-T standard certificates to encode the public keys 120 additional certificates which will be included in the system keyring by 199 trusted certificates can be provided in a PEM-encoded file referenced by the
|
| /linux/drivers/platform/x86/hp/ |
| H A D | Kconfig | 73 using digital certificates and public-key cryptography that eliminate
|
| /linux/arch/s390/kernel/ |
| H A D | ipl.c | 2420 list_add_tail(&cert->list, &report->certificates); in ipl_report_add_certificate() 2442 INIT_LIST_HEAD(&report->certificates); in ipl_report_init() 2490 list_for_each_entry(cert, &report->certificates, list) { in ipl_report_finish() 2497 list_for_each_entry(cert, &report->certificates, list) { in ipl_report_finish() 2515 list_for_each_entry_safe(cert, ncert, &report->certificates, list) in ipl_report_free()
|
| /linux/Documentation/crypto/ |
| H A D | asymmetric-keys.rst | 375 certificates, with a separate, restricted keyring set up for each 378 # Create and populate a keyring for root certificates 395 one of the root certificates.
|
| /linux/arch/s390/ |
| H A D | Kconfig | 592 bool "Get user certificates via DIAG320" 597 certificates via DIAG 0x320. 599 These certificates will be made available via the keyring named
|
| /linux/Documentation/networking/ |
| H A D | tls-handshake.rst | 84 Authentication material such as x.509 certificates, private certificate
|
| /linux/arch/powerpc/boot/dts/ |
| H A D | turris1x.dts | 300 label = "certificates";
|
| /linux/drivers/staging/greybus/Documentation/firmware/ |
| H A D | firmware-management | 290 cryptographic certificates held by the Interface for use in Component
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | verity.rst | 150 also gain new certificates at run time if they are signed by a certificate
|
| /linux/security/integrity/ima/ |
| H A D | Kconfig | 282 X509 certificates signed by a trusted key on the
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm-security.rst | 158 Every TPM comes shipped with a couple of X.509 certificates for the
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-firmware-attributes | 306 Admin and System certificates are supported from 2025 systems onward.
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | amd-memory-encryption.rst | 635 certificates from userspace for each SNP attestation request the guest issues.
|
| /linux/Documentation/filesystems/ |
| H A D | fsverity.rst | 483 root user can add trusted X.509 certificates to this keyring using 490 file's actual digest against this signature, using the certificates
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 603 Controls loading IMA certificates through the Kconfigs,
|
| /linux/Documentation/process/ |
| H A D | maintainer-pgp-guide.rst | 855 looking up public keys, GnuPG will validate DNSSEC or TLS certificates,
|