Searched full:authentication (Results 1 – 25 of 74) sorted by relevance
123
| /Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 2 Pointer authentication in AArch64 Linux
9 This document briefly describes the provision of pointer authentication
16 The ARMv8.3 Pointer Authentication extension adds primitives that can be
20 The extension uses a Pointer Authentication Code (PAC) to determine
38 (APDAKey, APDBKey), and one for generic authentication (APGAKey).
49 Presence of address authentication functionality is advertised via
50 HWCAP_PACA, and generic authentication functionality via HWCAP_PACG.
57 with HINT space pointer authentication instructions protecting
59 with or without pointer authentication support.
72 authentication is present, the kernel will expose the position of TTBR0
[all …]
|
| D | index.rst | 24 pointer-authentication
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-firmware-attributes | 149 What: /sys/class/firmware-attributes/*/authentication/
156 Devices support various authentication mechanisms which can be exposed
166 Change in any of these two authentication methods will also generate an
171 <attr> authentication is enabled.
175 The type of authentication used.
195 The means of authentication. This attribute is mandatory.
256 Available for HDD and NVMe authentication to set 'user' or 'master'
265 Used with HDD and NVME authentication to set the drive index
270 These attributes are used for certificate based authentication. This is
272 based authentication.
[all …]
|
| D | sysfs-driver-intel_sdsi | 56 (WO) Used to write an Authentication Key Certificate (AKC) to
68 previously provisioned AKC file. Upon successful authentication,
|
| /Documentation/filesystems/ |
| D | ubifs-authentication.rst | 3 .. UBIFS Authentication
8 UBIFS Authentication Support
33 can be used to get full data authentication at the block layer.
37 authentication for UBIFS. Since UBIFS uses fscrypt for file contents and file
38 name encryption, the authentication system could be tied into fscrypt such that
40 be possible to use UBIFS authentication without using encryption.
206 UBIFS Authentication
209 This chapter introduces UBIFS authentication which enables UBIFS to verify
216 UBIFS authentication enables detection of offline data modification. While it
221 UBIFS authentication will not protect against rollback of full flash contents.
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 6 implement RPCGSS authentication in kernel RPC servers such as the NFS
9 purposes of authentication.)
23 The RPCGSS Authentication method describes a way to perform GSSAPI
24 Authentication for NFS. Although GSSAPI is itself completely mechanism
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 213 system call family, the consumer must set the authentication tag size.
214 To set the authentication tag size, the caller must use the setsockopt
235 - specification of the associated authentication data (AAD) with the
265 - associated authentication data (AAD)
267 - authentication tag
269 The sizes of the AAD and the authentication tag are provided with the
279 - AEAD decryption input: AAD \|\| ciphertext \|\| authentication tag
284 - AEAD encryption output: ciphertext \|\| authentication tag
394 - ALG_SET_AEAD_AUTHSIZE -- Setting the authentication tag size for
395 AEAD ciphers. For a encryption operation, the authentication tag of
[all …]
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 17 FEK decryption is called authentication token and, currently, can be stored in a
25 authentication token in its payload with a FEKEK randomly generated by the
30 authentication token, which content is well known, but only the FEKEK in
|
| /Documentation/driver-api/media/drivers/ |
| D | ipu6.rst | 31 interrupt handling, firmware authentication and global timer sync.
60 Security and firmware authentication
64 undergo an authentication process before it is allowed to executed on the IPU6
66 (CSE) to complete authentication process. The CSE is responsible of
68 into an isolated memory region. Firmware authentication process is implemented
122 metadata are defined by CSE and used by CSE for authentication. Module data is
127 ``FW_SOURCE_BASE`` register. Finally the CSE will do authentication for this
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,sm8550-pas.yaml | 7 title: Qualcomm SM8550 Peripheral Authentication Service
13 Qualcomm SM8550 SoC Peripheral Authentication Service loads and boots firmware
55 - description: Memory region for main Firmware authentication
56 - description: Memory region for Devicetree Firmware authentication
|
| D | qcom,sa8775p-pas.yaml | 7 title: Qualcomm SA8775p Peripheral Authentication Service
13 Qualcomm SA8775p SoC Peripheral Authentication Service loads and boots firmware
47 - description: Memory region for main Firmware authentication
|
| D | qcom,sc8180x-pas.yaml | 7 title: Qualcomm SC8180X Peripheral Authentication Service
13 Qualcomm SC8180X SoC Peripheral Authentication Service loads and boots
|
| D | qcom,pas-common.yaml | 7 title: Qualcomm Peripheral Authentication Service Common Properties
13 Common properties of Qualcomm SoCs Peripheral Authentication Service.
|
| D | qcom,qcs404-pas.yaml | 7 title: Qualcomm QCS404 Peripheral Authentication Service
13 Qualcomm QCS404 SoC Peripheral Authentication Service loads and boots
|
| D | qcom,sdx55-pas.yaml | 7 title: Qualcomm SDX55 Peripheral Authentication Service
13 Qualcomm SDX55 SoC Peripheral Authentication Service loads and boots firmware
|
| D | qcom,sm6375-pas.yaml | 7 title: Qualcomm SM6375 Peripheral Authentication Service
13 Qualcomm SM6375 SoC Peripheral Authentication Service loads and boots
|
| D | qcom,sm6115-pas.yaml | 7 title: Qualcomm SM6115 Peripheral Authentication Service
13 Qualcomm SM6115 SoC Peripheral Authentication Service loads and boots
|
| D | qcom,sc8280xp-pas.yaml | 7 title: Qualcomm SC8280XP Peripheral Authentication Service
13 Qualcomm SC8280XP SoC Peripheral Authentication Service loads and boots
|
| D | qcom,sm6350-pas.yaml | 7 title: Qualcomm SM6350 Peripheral Authentication Service
13 Qualcomm SM6350 SoC Peripheral Authentication Service loads and boots
|
| D | qcom,sm8150-pas.yaml | 7 title: Qualcomm SM8150/SM8250 Peripheral Authentication Service
13 Qualcomm SM8150/SM8250 SoC Peripheral Authentication Service loads and boots
|
| /Documentation/networking/ |
| D | tls-offload.rst | 54 On the receive side if the device handled decryption and authentication
133 * crypto processing state (partial blocks, partial authentication tag, etc.)
140 crypto operations and authentication regardless of segmentation. For this
146 * partial authentication tag (all data had been seen but part of the
147 authentication tag has to be written or read from the subsequent segment)
156 The kernel stack performs record framing reserving space for the authentication
167 The device performs encryption and authentication of the record data.
168 It replaces the authentication tag and TCP checksum with correct values.
180 decryption, authentication for each record in the packet). The device leaves
221 data (to be able to insert the authentication tag) and move onto handling
[all …]
|
| D | mac80211-auth-assoc-deauth.txt | 2 # This outlines the Linux authentication/association and
13 alt authentication needed (not FT)
|
| D | tls-handshake.rst | 12 addition to peer authentication.
84 Authentication material such as x.509 certificates, private certificate
126 during this type of handshake. Only server authentication (ie the client
188 | | authentication failed |
194 | -ENOKEY | Missing authentication material |
|
| /Documentation/target/ |
| D | target-export-device | 73 # Disable authentication
74 echo 0 > $ISCSI_DIR/$IQN/tpgt_1/attrib/authentication
|
| /Documentation/translations/zh_TW/arch/arm64/ |
| D | elf_hwcaps.rst | 158 如 Documentation/arch/arm64/pointer-authentication.rst 所描述，
163 如 Documentation/arch/arm64/pointer-authentication.rst 所描述，
|
123