| /linux/drivers/crypto/ |
| H A D | Kconfig | 23 operations with supported algorithms.
42 tristate "PadLock driver for SHA1 and SHA256 algorithms"
48 Use VIA PadLock for SHA1/SHA256 algorithms.
177 tristate "PAES cipher algorithms"
186 AES cipher algorithms for use with protected key.
308 you want to use the OMAP modules for any of the crypto algorithms.
323 want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
337 want to use the OMAP module for AES algorithms.
347 want to use the OMAP module for DES and 3DES algorithms. Currently
388 algorithms execution.
[all …]
|
| /linux/crypto/ |
| H A D | Kconfig | 3 # Generic algorithms support
61 This option provides the API for cryptographic algorithms.
184 registration time if algorithms are dynamically loaded later.
208 tristate "Null algorithms"
213 These are 'Null' algorithms, used by IPsec, which do nothing.
265 algorithms in the kernel. It should not be enabled in production
344 One of the Russian cryptographic standard algorithms (called GOST
345 algorithms). Only signature verification is implemented.
364 AES cipher algorithms (Rijndael)(FIPS-197, ISO/IEC 18033-3)
382 AES cipher algorithms (Rijndael)(FIPS-197, ISO/IEC 18033-3)
[all …]
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | zram.rst | 80 currently selected (shown in square brackets) compression algorithms,
86 #show supported compression algorithms
94 algorithms that are supported by zram.
99 Compression algorithms may support specific parameters which can be
103 For example, several compression algorithms support `level` parameter.
104 In addition, certain compression algorithms support pre-trained dictionaries,
105 which significantly change algorithms' characteristics. In order to configure
120 Parameters are algorithm specific: not all algorithms support pre-trained
121 dictionaries, not all algorithms support `level`. Furthermore, for certain
122 algorithms `level` controls the compression level (the higher the value the
[all …]
|
| /linux/Documentation/crypto/ |
| H A D | api-intro.rst | 23 At the lowest level are algorithms, which register dynamically with the
28 abstraction to the underlying algorithms. However, at the user
35 [algorithm api] (for registering algorithms)
100 Adding New Algorithms
112 Algorithms submitted must also be generally patent-free (e.g. IDEA
117 Also check for any RFCs which may relate to the use of specific algorithms,
119 Cipher Algorithms").
188 Original developers of the crypto algorithms:
|
| H A D | devel-algos.rst | 1 Developing Cipher Algorithms
40 successfully registered all the given algorithms; if it fails partway
44 return value. Don't try to unregister algorithms that aren't
111 The registration of multi-block cipher algorithms is one of the most
|
| H A D | intro.rst | 18 The kernel crypto API refers to all algorithms as "transformations".
34 transformations (such as CRC or even compression algorithms) that can
|
| /linux/net/ipv6/ |
| H A D | Kconfig | 57 AH can be used with various authentication algorithms. Besides
59 implementations of the algorithms that RFC 8221 lists as MUST be
60 implemented. If you need any other algorithms, you'll need to enable
62 implementations of any needed algorithms when available.
72 ESP can be used with various encryption and authentication algorithms.
74 implementations of the algorithms that RFC 8221 lists as MUST be
75 implemented. If you need any other algorithms, you'll need to enable
77 implementations of any needed algorithms when available.
|
| /linux/Documentation/filesystems/ |
| H A D | btrfs.rst | 21 * Checksums on data and metadata (multiple algorithms available)
22 * Compression (multiple algorithms available)
26 * Integrated multiple device support, with several raid algorithms
|
| /linux/fs/crypto/ |
| H A D | Kconfig | 18 # allows the algorithms to be built as modules when all the filesystems are,
21 # Note: this option only pulls in the algorithms that filesystem encryption
27 # algorithms, not any per-architecture optimized implementations. It is
|
| /linux/drivers/crypto/hisilicon/ |
| H A D | Kconfig | 36 It provides AES, SM4, and 3DES algorithms with ECB
37 CBC, and XTS cipher mode, and AEAD algorithms.
76 accelerator, which can accelerate RSA and DH algorithms.
|
| /linux/drivers/crypto/intel/keembay/ |
| H A D | Kconfig | 73 sm3, as well as the HMAC variant of these algorithms.
84 Enables support for sha224 and hmac(sha224) algorithms in the Intel
86 algorithms.
|
| /linux/drivers/crypto/allwinner/ |
| H A D | Kconfig | 22 and SHA1 and MD5 hash algorithms.
79 Say y to enable support for hash algorithms.
139 Say y to enable support for hash algorithms.
|
| /linux/include/linux/ |
| H A D | crc8.h | 46 * regular bit order (lsb first). Polynomials in CRC algorithms are typically
64 * reverse bit order (msb first). Polynomials in CRC algorithms are typically
95 * "A Painless Guide to CRC Error Detection Algorithms", ver 3, Aug 1993
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | nvidia,tegra234-se-aes.yaml | 7 title: NVIDIA Tegra Security Engine for AES algorithms
11 algorithms - AES-ECB, AES-CBC, AES-OFB, AES-XTS, AES-CTR, AES-GCM, AES-CCM,
|
| /linux/net/ipv4/ |
| H A D | Kconfig | 346 AH can be used with various authentication algorithms. Besides
348 implementations of the algorithms that RFC 8221 lists as MUST be
349 implemented. If you need any other algorithms, you'll need to enable
351 implementations of any needed algorithms when available.
361 ESP can be used with various encryption and authentication algorithms.
363 implementations of the algorithms that RFC 8221 lists as MUST be
364 implemented. If you need any other algorithms, you'll need to enable
366 implementations of any needed algorithms when available.
|
| /linux/Documentation/ABI/testing/ |
| H A D | ima_policy | 75 appraise_algos:= comma-separated list of hash algorithms
78 of these two algorithms.
160 restricts the hash algorithms allowed when writing to the
|
| H A D | sysfs-driver-uacce | 40 What: /sys/class/uacce/<dev_name>/algorithms
44 Description: Algorithms supported by this accelerator, separated by new line.
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 33 technique that often cannot be replaced with lockless algorithms. As we
38 algorithms often endangers to ability to do robust reviews of said code.
40 data structures, instead of lockless algorithms. Furthermore, there are
|
| /linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 110 A specialized processor that implements a set of algorithms for
111 processing image data. ISPs may implement algorithms for lens
114 algorithms (e.g. automatic exposure, white balance and focus).
|
| /linux/include/crypto/ |
| H A D | aes.h | 3 * Common values for AES algorithms
35 * validate key length for AES algorithms
|
| /linux/drivers/mtd/ |
| H A D | Kconfig | 85 You may find that the algorithms used in this code are patented
102 You may find that the algorithms used in this code are patented
127 You may find that the algorithms used in this code are patented
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_uncore_frequency_scaling.rst | 17 performance, SoCs have internal algorithms for scaling uncore frequency. These
18 algorithms monitor workload usage of uncore and set a desirable frequency.
131 per watt. With this feature hardware power management algorithms
|
| /linux/drivers/crypto/qce/ |
| H A D | common.h | 35 /* cipher algorithms */
40 /* hash and hmac algorithms */
|
| /linux/fs/verity/ |
| H A D | hash_algs.c | 3 * fs-verity hash algorithms
12 /* The hash algorithms supported by fs-verity */
220 * Sanity check the hash algorithms (could be a build-time check, but in fsverity_check_hash_algs()
|
| /linux/fs/f2fs/ |
| H A D | Kconfig | 27 layout, but also for selecting allocation and cleaning algorithms.
100 multiple back-end compression algorithms are supported.
|