Home
last modified time | relevance | path

Searched refs:authentication (Results 1 – 25 of 43) sorted by relevance

12

/Zephyr-Core-3.4.0/samples/bluetooth/peripheral_hids/
DKconfig7 bool "Enable passkey authentication"
10 Enable the passkey authentication callback and register the GATT
11 read and and write attributes as authentication required.
DREADME.rst13 In the default configuration the sample uses passkey authentication (displays a
16 To disable authentication and just use encrypted channels instead, build the
/Zephyr-Core-3.4.0/subsys/mgmt/hawkbit/
DKconfig55 prompt "Hawkbit DDI API authentication modes"
59 bool "No authentication security"
61 No authentication security for the Hawkbit DDI API.
64 bool "Use target security token authentication"
66 Use target security token authentication for the Hawkbit DDI API.
69 bool "Use gateway security token authentication"
71 Use gateway security token authentication for the Hawkbit DDI API.
81 authentication mode.
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/api/mesh/
Dprovisioning.rst44 Of Band information, such as the device's public key or an authentication
122 The Provisioning API supports the following authentication methods for the
125 * **Static OOB:** An authentication value is assigned to the device in
128 * **Input OOB:** The user inputs the authentication value. The available input
130 * **Output OOB:** Show the user the authentication value. The available output
133 The application must provide callbacks for the supported authentication
138 When an Output OOB action is selected, the authentication value should be
151 If Provisionee wants to mandate OOB authentication, it is mandatory to use
175 Depending on the choice of public key exchange mechanism and authentication method,
Dshell.rst263 * ``AuthType``: If present, the OOB authentication type used for provisioning.
293 …Input a numeric OOB authentication value. Only valid when prompted by the shell during provisionin…
295 * ``Number``: Decimal authentication number.
301 …Input an alphanumeric OOB authentication value. Only valid when prompted by the shell during provi…
303 * ``String``: Unquoted alphanumeric authentication string.
309 …Set or clear the static OOB authentication value. The static OOB authentication value must be set …
339 …ner device, instruct the unprovisioned device to use the specified Input OOB authentication action.
352 …er device, instruct the unprovisioned device to use the specified Output OOB authentication action.
365 …truct the unprovisioned device to use static OOB authentication, and use the given static authenti…
371 …From the provisioner device, don't use any authentication when provisioning new devices. This is t…
/Zephyr-Core-3.4.0/subsys/net/lib/config/
DKconfig164 1 authentication only with a 4 bytes length tag
165 2 authentication only with a 8 bytes length tag
166 3 authentication only with a 16 bytes length tag
168 5 encryption/authentication with a 4 bytes length tag
169 6 encryption/authentication with a 8 bytes length tag
170 7 encryption/authentication with a 16 bytes length tag
/Zephyr-Core-3.4.0/subsys/bluetooth/services/
DKconfig.hrs26 bool "Require encryption and authentication for access"
/Zephyr-Core-3.4.0/subsys/bluetooth/services/ias/
DKconfig.ias25 bool "Require encryption and authentication for write access"
/Zephyr-Core-3.4.0/subsys/net/l2/ppp/
DKconfig62 bool "PAP authentication protocol"
65 Enable support for PAP authentication protocol.
/Zephyr-Core-3.4.0/subsys/net/l2/
DKconfig43 Level 1 (BT_SECURITY_L1) = No encryption or authentication required
45 Level 3 (BT_SECURITY_L3) = Encryption and authentication required
/Zephyr-Core-3.4.0/subsys/bluetooth/host/
Dssp.c609 evt->authentication); in bt_hci_io_capa_resp()
611 if (evt->authentication > BT_HCI_GENERAL_BONDING_MITM) { in bt_hci_io_capa_resp()
632 conn->br.remote_auth = evt->authentication; in bt_hci_io_capa_resp()
680 cp->authentication = auth; in bt_hci_io_capa_req()
DCMakeLists.txt121 channels that would otherwise require encryption/authentication in order to
/Zephyr-Core-3.4.0/modules/
DKconfig.tinycrypt29 message authentication code.
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/
Dbluetooth-shell.rst265 * **1** No encryption and no authentication;
266 * **2** Encryption and no authentication;
267 * **3** Encryption and authentication;
270 To enable security, use the :code:`bt security <level>` command. For levels requiring authentication
271 (level 3 and above), you must first set the authentication method. To do it, you can use the
279 Enabling authentication requires the devices to be bondable. By default the shell is bondable. You
Dbluetooth-arch.rst336 No encryption and no authentication.
339 Encryption but no authentication (no MITM protection).
342 Encryption and authentication using the legacy pairing method
346 Encryption and authentication using the LE Secure Connections
/Zephyr-Core-3.4.0/doc/connectivity/networking/api/
Dmqtt.rst154 credentials that the MQTT library should use for authentication. We do not specify
157 authentication. Finally, we enforce peer certificate verification by setting
/Zephyr-Core-3.4.0/doc/services/crypto/
Dtinycrypt.rst27 * Type of primitive: Message authentication code.
57 * Type of primitive: Message authentication code.
192 produce the same authentication tag). TinyCrypt CCM implementation
207 authentication-only mode on the associated data).
/Zephyr-Core-3.4.0/samples/subsys/mgmt/hawkbit/
DREADME.rst71 --hawkbit.server.ddi.security.authentication.anonymous.enabled=true
237 Change authentication security from false to true.
241 hawkbit.server.ddi.security.authentication.anonymous.enabled=true
/Zephyr-Core-3.4.0/subsys/mgmt/osdp/
DKconfig81 authentication.
/Zephyr-Core-3.4.0/doc/security/
Dsecure-coding.rst77 protection scheme, e.g., after successful authentication.
163 authentication, such as requiring both a password and a hardware
164 token, is stronger than single-factor authentication)
206 scripting, missing authentication, and missing authorization. See the
/Zephyr-Core-3.4.0/samples/tfm_integration/psa_protected_storage/
DREADME.rst12 optional authentication and rollback protection. The default crypto algorithm is ``AES-128-GCM``.
/Zephyr-Core-3.4.0/subsys/net/l2/ieee802154/
DKconfig149 IEEE 802.15.4 soft MAC will use to run authentication, encryption and
/Zephyr-Core-3.4.0/soc/arm/microchip_mec/
DKconfig24 authentication and all other Boot-ROM loader features. Refer to the MCHP
/Zephyr-Core-3.4.0/modules/hal_nordic/
DKconfig47 bool "nRF 802.15.4 AES-CCM* authentication & encryption"
/Zephyr-Core-3.4.0/doc/develop/west/
Dworkspaces.rst95 authentication enabled, and may be preferable to storing your account password
96 in plain text even if two-factor authentication is disabled.)

12