| /linux-6.15/Documentation/admin-guide/ |
| H A 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 38 Configuring module signing 41 The module signing facility is enabled by going to the 97 (4) :menuselection:`File name or PKCS#11 URI of module signing key` 126 Generating signing keys 217 Manually signing modules [all …]
|
| H A D | index.rst | 99 module-signing
|
| /linux-6.15/certs/ |
| H A 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. 35 Use an elliptic curve key (NIST P384) for module signing. Use 39 Note: Remove all ECDSA signing keys, e.g. certs/signing_key.pem, 64 system keyring. Any certificate used for module signing is implicitly 106 linking code signing keys with imputed trust to the secondary
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-driver-intel-m10-bmc-sec-update | 36 signing keys for the static region. The standard bitmap 44 signing keys for the partial reconfiguration region. The 52 signing keys for the BMC. The standard bitmap list format
|
| H A D | sysfs-class-firmware-attributes | 271 used in conjunction with a signing server as an alternative to password 274 from the signing server. 327 It requires configuring an endorsement (kek) and signing certificate (sk). 439 signatures when setting the signing key. When written,
|
| /linux-6.15/Documentation/kbuild/ |
| H A 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-6.15/fs/smb/client/ |
| H A D | smb2transport.c | 422 struct derivation signing; member 463 rc = generate_key(ses, ptriplet->signing.label, in generate_smb3signingkey() 464 ptriplet->signing.context, in generate_smb3signingkey() 470 rc = generate_key(ses, ptriplet->signing.label, in generate_smb3signingkey() 471 ptriplet->signing.context, in generate_smb3signingkey() 534 d = &triplet.signing; in generate_smb30signingkey() 563 d = &triplet.signing; in generate_smb311signingkey()
|
| /linux-6.15/fs/smb/server/ |
| H A D | server.h | 33 short signing; member
|
| H A D | auth.c | 781 const struct derivation *signing) in generate_smb3signingkey() argument 791 if (conn->dialect >= SMB30_PROT_ID && signing->binding) in generate_smb3signingkey() 796 rc = generate_key(conn, sess, signing->label, signing->context, key, in generate_smb3signingkey() 801 if (!(conn->dialect >= SMB30_PROT_ID && signing->binding)) in generate_smb3signingkey()
|
| H A D | Kconfig | 42 compound requests, multi-credit, packet signing, RDMA(smbdirect),
|
| H A D | ksmbd_netlink.h | 88 __s32 signing; /* Signing enabled */ member
|
| /linux-6.15/kernel/module/ |
| H A D | Makefile | 15 obj-$(CONFIG_MODULE_SIG) += signing.o
|
| /linux-6.15/crypto/asymmetric_keys/ |
| H A D | mscode.asn1 | 1 --- Microsoft individual code signing data blob parser
|
| /linux-6.15/Documentation/crypto/ |
| H A 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-6.15/Documentation/translations/zh_CN/admin-guide/ |
| H A D | index.rst | 109 * module-signing
|
| /linux-6.15/Documentation/translations/zh_TW/admin-guide/ |
| H A D | index.rst | 111 * module-signing
|
| /linux-6.15/Documentation/admin-guide/cifs/ |
| H A D | usage.rst | 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 725 also packet signing. Authentication (may/must) 727 the signing flags. Specifying two different password 733 (NTLMv2 and packet signing allowed). Some SecurityFlags 736 may use packet signing 0x00001 [all …]
|
| H A D | todo.rst | 18 support for faster packet signing (GMAC), 121 and when signing is disabled to request larger read sizes (larger than
|
| H A D | introduction.rst | 29 signing, large files, Unicode support and other internationalization
|
| /linux-6.15/ |
| H A D | .gitignore | 154 # Leavings from module signing
|
| /linux-6.15/Documentation/security/ |
| H A D | ipe.rst | 68 3. Simplicity of signing: 73 * The signature supports an x.509-based signing infrastructure. 181 signing as a process. Signing, as a process, is typically done with a 183 enforcement systems. It is also important that, when signing something, that 184 the signer is aware of what they are signing. A binary policy can cause 187 submitted for signing.
|
| H A D | digsig.rst | 81 The signing and key management utilities evm-utils provide functionality
|
| /linux-6.15/security/ipe/ |
| H A D | Kconfig | 92 enabled and it has a valid builtin signature whose signing cert
|
| /linux-6.15/Documentation/filesystems/nfs/ |
| H A D | rpc-server-gss.rst | 36 - integrity/privacy protection (signing and encrypting of individual
|
| /linux-6.15/Documentation/process/ |
| H A D | maintainer-pgp-guide.rst | 127 - **[S]** keys can be used for signing 146 subkeys, 3 valid signing subkeys, but only one valid certification 198 separate signing subkey:: 255 such as when making changes to your own key or signing other people's 279 like editing identities, adding or revoking subkeys, or signing other 736 this reason, most kernel developers don't bother signing their commits 801 further configuration. You can start signing your patches by installing
|