| /linux-5.19.10/Documentation/admin-guide/ |
| D | module-signing.rst | 1 Kernel module signing facility
7 .. - Configuring module signing.
8 .. - Generating signing keys.
10 .. - Manually signing modules.
21 The kernel module signing facility cryptographically signs modules during
24 or modules signed with an invalid key. Module signing increases security by
38 Configuring module signing
41 The module signing facility is enabled by going to the
96 (4) :menuselection:`File name or PKCS#11 URI of module signing key`
100 ``certs/signing_key.pem`` will disable the autogeneration of signing keys
[all …]
|
| D | index.rst | 104 module-signing
|
| /linux-5.19.10/certs/ |
| D | Kconfig | 5 string "File name or PKCS#11 URI of module signing key"
16 certificate as described in Documentation/admin-guide/module-signing.rst
19 prompt "Type of module signing key to be generated"
22 The type of module signing key type to generate. This option
28 Use an RSA key for module signing.
34 Use an elliptic curve key (NIST P384) for module signing. Consider
37 Note: Remove all ECDSA signing keys, e.g. certs/signing_key.pem,
62 system keyring. Any certificate used for module signing is implicitly
|
| /linux-5.19.10/Documentation/kbuild/ |
| D | reproducible-builds.rst | 74 Module signing
79 modules being unreproducible. However, including a signing key with
80 your source would presumably defeat the purpose of signing modules.
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/fs/cifs/ |
| D | smb2transport.c | 391 struct derivation signing; member
422 rc = generate_key(ses, ptriplet->signing.label, in generate_smb3signingkey()
423 ptriplet->signing.context, in generate_smb3signingkey()
429 rc = generate_key(ses, ptriplet->signing.label, in generate_smb3signingkey()
430 ptriplet->signing.context, in generate_smb3signingkey()
494 d = &triplet.signing; in generate_smb30signingkey()
523 d = &triplet.signing; in generate_smb311signingkey()
|
| /linux-5.19.10/fs/ksmbd/ |
| D | server.h | 33 short signing; member
|
| D | auth.c | 749 const struct derivation *signing) in generate_smb3signingkey() argument
759 if (sess->conn->dialect >= SMB30_PROT_ID && signing->binding) in generate_smb3signingkey()
764 rc = generate_key(sess, signing->label, signing->context, key, in generate_smb3signingkey()
769 if (!(sess->conn->dialect >= SMB30_PROT_ID && signing->binding)) in generate_smb3signingkey()
|
| D | Kconfig | 41 compound requests, multi-credit, packet signing, RDMA(smbdirect),
|
| D | ksmbd_netlink.h | 83 __s32 signing; /* Signing enabled */ member
|
| D | transport_ipc.c | 292 server_conf.signing = req->signing; in ipc_server_config_on_startup()
|
| /linux-5.19.10/kernel/module/ |
| D | Makefile | 12 obj-$(CONFIG_MODULE_SIG) += signing.o
|
| /linux-5.19.10/crypto/asymmetric_keys/ |
| D | mscode.asn1 | 1 --- Microsoft individual code signing data blob parser
|
| /linux-5.19.10/Documentation/crypto/ |
| D | asymmetric-keys.rst | 343 The kernel builtin trusted keyring will be searched for the signing key.
354 signing key. If the secondary trusted keyring is not configured, this
367 a group of keys may be searched for the signing key by providing the
371 within the destination keyring will also be searched for signing keys.
394 keyring, we can be certain that it has a valid signing chain going back to
415 keyring, we can be certain that there is a valid signing chain going back
419 In all of these cases, if the signing key is found the signature of the key to
420 be linked will be verified using the signing key. The requested key is added
|
| /linux-5.19.10/Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 109 * module-signing
|
| /linux-5.19.10/Documentation/translations/zh_TW/admin-guide/ |
| D | index.rst | 109 module-signing
|
| /linux-5.19.10/Documentation/admin-guide/cifs/ |
| D | usage.rst | 82 and encrypted shares and stronger signing and authentication algorithms.
224 cifs signing enabled (and the physical network is insecure), consider use
642 Must use packet signing (helps avoid unwanted data modification
643 by intermediate systems in the route). Note that signing
673 Use Kerberos authentication and packet signing
677 Use NTLM password hashing with signing (if
679 server requires signing also can be the default)
683 Use NTLMv2 password hashing with packet signing
724 also packet signing. Authentication (may/must)
726 the signing flags. Specifying two different password
[all …]
|
| D | introduction.rst | 29 signing, large files, Unicode support and other internationalization
|
| D | todo.rst | 123 and when signing is disabled to request larger read sizes (larger than
|
| /linux-5.19.10/ |
| D | .gitignore | 138 # Leavings from module signing
|
| /linux-5.19.10/Documentation/security/ |
| D | digsig.rst | 81 The signing and key management utilities evm-utils provide functionality
|
| /linux-5.19.10/Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 36 - integrity/privacy protection (signing and encrypting of individual
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-class-firmware-attributes | 251 used in conjunction with a signing server as an alternative to password
254 from the signing server.
|
| /linux-5.19.10/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 161 - **[S]** key can be used for signing
220 signing subkey::
237 recommend that you create an ECC signing subkey for your kernel
295 such as when making changes to your own key or signing other people's
319 like editing identities, adding or revoking subkeys, or signing other
789 this reason, most kernel developers don't bother signing their commits
|
| D | changes.rst | 145 Module signing and external certificate handling use the OpenSSL program and
148 You will need openssl to build kernels 3.7 and higher if module signing is
|
| /linux-5.19.10/Documentation/ |
| D | Changes | 145 Module signing and external certificate handling use the OpenSSL program and
148 You will need openssl to build kernels 3.7 and higher if module signing is
|