| /hal_espressif-2.7.6/examples/provisioning/wifi_prov_mgr/ |
| D | wifi_prov_mgr_test.py | 59 security = esp_prov.get_security(secver, pop, verbose)
60 if security is None:
77 if not esp_prov.establish_session(transport, security):
81 if not esp_prov.custom_data(transport, security, 'My Custom Data'):
85 if not esp_prov.send_wifi_config(transport, security, ap_ssid, ap_password):
89 if not esp_prov.apply_wifi_config(transport, security):
92 if not esp_prov.wait_wifi_connected(transport, security):
|
| /hal_espressif-2.7.6/examples/provisioning/legacy/ble_prov/ |
| D | ble_prov_test.py | 59 security = esp_prov.get_security(secver, pop, verbose)
60 if security is None:
73 if not esp_prov.establish_session(transport, security):
77 if not esp_prov.send_wifi_config(transport, security, ap_ssid, ap_password):
81 if not esp_prov.apply_wifi_config(transport, security):
84 if not esp_prov.wait_wifi_connected(transport, security):
|
| /hal_espressif-2.7.6/examples/provisioning/legacy/softap_prov/ |
| D | softap_prov_test.py | 74 security = esp_prov.get_security(secver, pop, verbose)
75 if security is None:
88 if not esp_prov.establish_session(transport, security):
92 if not esp_prov.send_wifi_config(transport, security, ap_ssid, ap_password):
96 if not esp_prov.apply_wifi_config(transport, security):
99 if not esp_prov.wait_wifi_connected(transport, security):
|
| /hal_espressif-2.7.6/components/protocomm/proto/ |
| D | session.proto | 6 /* Allowed values for the type of security
16 SecSchemeVersion sec_ver = 2; /*!< Type of security */
18 Sec0Payload sec0 = 10; /*!< Payload data in case of security 0 */
19 Sec1Payload sec1 = 11; /*!< Payload data in case of security 1 */
|
| /hal_espressif-2.7.6/docs/en/api-reference/bluetooth/ |
| D | esp_gap_ble.rst | 16 …is a SMP security client demo and its tutorial. This demo initiates its security parameters and ac…
21 * This is a SMP security server demo and its tutorial. This demo initiates its security parameters …
|
| /hal_espressif-2.7.6/docs/en/api-reference/provisioning/ |
| D | provisioning.rst | 6 …nd/or other custom configuration using various transports and different security schemes. Dependin…
10 …security scheme to secure the data that is exchanged in the provisioning process. Some application…
68 …s the security scheme needs to be selected by the application developers. Following considerations…
71 … unique per device secret to be entered on the provisioning client as a security measure to make s…
73 There are two levels of security schemes. The developer may select one or combination depending on …
75 …security with unique per-device passphrase. Per-device unique passphrase can also act as a proof-o…
76 …security (*security1*) that provides data protection and authentication (through proof-of-possessi…
96 …doc:`protocomm` (Protocol Communication) which provides a framework for security schemes and trans…
98 …security scheme. Each transport in the protocomm has a concept of an "end-point" which corresponds…
102 At present unified provisioning supports two security schemes:
[all …]
|
| D | protocomm.rst | 9 * Communication security at application level -
10 * protocomm_security0 (no security)
14 …gh users can implement their own security (even without using protobuf). One can even use protocom…
77 /* Set security for communication at application level. Just like for
78 * request handlers, setting security creates an endpoint and registers
80 * protocomm_security0. Only one type of security can be set for a
104 /* Remove security endpoint identified by it's name */
|
| /hal_espressif-2.7.6/examples/bluetooth/bluedroid/ble/gatt_security_server/tutorial/ |
| D | Gatt_Security_Server_Example_Walkthrough.md | 5 In this document, a description of the security GATT Server BLE example for the ESP32 is presented.…
7 …security involves three interrelated concepts: pairing, bonding and encryption. Pairing concerns w…
9 This document only describes the security configuration. The rest of the GATT server functionalitie…
13 …security parameters in order to define how the pairing request and response are going to be built.…
17 * *Authorization Request*: indicates the requested security properties such as Bonding, Secure Conn…
94 The security parameters set previously are stored locally to be used later when the master device c…
98 //start security connect with peer device when receive the connect event sent by the master.
109 …CRYPT_NO_MITM` lies in the fact that a previous connection might have a security level that needs …
134 …s done successfully, the keys indicated by the `init_key` and `rsp_key` security parameters are ex…
194 …encrypted permissions and a peer device that does not have the required security clearance tries t…
[all …]
|
| /hal_espressif-2.7.6/examples/provisioning/legacy/console_prov/main/ |
| D | app_prov.c | 40 int security; /*!< Type of security to use with protocomm */ member
76 if (g_prov->security == 0) { in app_prov_start_service()
78 } else if (g_prov->security == 1) { in app_prov_start_service()
273 esp_err_t app_prov_start_console_provisioning(int security, const protocomm_security_pop_t *pop) in app_prov_start_console_provisioning() argument
291 g_prov->security = security; in app_prov_start_console_provisioning()
|
| D | app_main.c | 63 int security = 0; in start_console_provisioning() local
68 security = 1; in start_console_provisioning()
80 ESP_ERROR_CHECK(app_prov_start_console_provisioning(security, pop)); in start_console_provisioning()
|
| /hal_espressif-2.7.6/components/protocomm/ |
| D | CMakeLists.txt | 2 include/security
7 "src/security/security0.c"
8 "src/security/security1.c"
|
| D | component.mk | 1 COMPONENT_ADD_INCLUDEDIRS := include/common include/security include/transports
3 COMPONENT_SRCDIRS := src/common src/security proto-c src/simple_ble src/transports
|
| /hal_espressif-2.7.6/examples/provisioning/legacy/custom_config/main/ |
| D | app_main.c | 63 int security = 0; in start_softap_provisioning() local
68 security = 1; in start_softap_provisioning()
81 CONFIG_EXAMPLE_SSID, CONFIG_EXAMPLE_PASS, security, pop)); in start_softap_provisioning()
|
| D | app_prov.c | 42 int security; /*!< Type of security to use with protocomm */ member
82 if (g_prov->security == 0) { in app_prov_start_service()
84 } else if (g_prov->security == 1) { in app_prov_start_service()
338 int security, const protocomm_security_pop_t *pop) in app_prov_start_softap_provisioning() argument
356 g_prov->security = security; in app_prov_start_softap_provisioning()
|
| /hal_espressif-2.7.6/examples/provisioning/legacy/ble_prov/main/ |
| D | app_prov.c | 49 int security; /*!< Type of security to use with protocomm */ member
135 if (g_prov->security == 0) { in app_prov_start_service()
137 } else if (g_prov->security == 1) { in app_prov_start_service()
335 esp_err_t app_prov_start_ble_provisioning(int security, const protocomm_security_pop_t *pop) in app_prov_start_ble_provisioning() argument
353 g_prov->security = security; in app_prov_start_ble_provisioning()
|
| D | app_main.c | 96 int security = 0; in start_ble_provisioning() local
101 security = 1; in start_ble_provisioning()
113 ESP_ERROR_CHECK(app_prov_start_ble_provisioning(security, pop)); in start_ble_provisioning()
|
| /hal_espressif-2.7.6/examples/bluetooth/bluedroid/ble/gatt_security_client/ |
| D | README.md | 7 This is the demo for users to use ESP BLE security APIs to connect to and encrypt with peer devices.
12 1.`esp_ble_gap_set_security_param` should be used to set the security parameters in the initial sta…
13 …iates the encryption, `esp_ble_gap_security_rsp` should be used to send security response to the p…
|
| /hal_espressif-2.7.6/examples/provisioning/legacy/softap_prov/main/ |
| D | app_prov.c | 40 int security; /*!< Type of security to use with protocomm */ member
79 if (g_prov->security == 0) { in app_prov_start_service()
81 } else if (g_prov->security == 1) { in app_prov_start_service()
324 int security, const protocomm_security_pop_t *pop) in app_prov_start_softap_provisioning() argument
342 g_prov->security = security; in app_prov_start_softap_provisioning()
|
| D | app_main.c | 67 int security = 0; in start_softap_provisioning() local
72 security = 1; in start_softap_provisioning()
100 ssid, CONFIG_EXAMPLE_PASS, security, pop)); in start_softap_provisioning()
|
| /hal_espressif-2.7.6/docs/zh_CN/api-guides/ |
| D | index.rst | 23 Flash 加密 <../security/flash-encryption>
34 :esp32: 安全启动 <../security/secure-boot-v1>
35 安全启动 V2 <../security/secure-boot-v2>
|
| /hal_espressif-2.7.6/docs/en/api-guides/ |
| D | index.rst | 23 Flash Encryption <../security/flash-encryption>
34 :esp32: Secure Boot <../security/secure-boot-v1>
35 Secure Boot V2 <../security/secure-boot-v2>
|
| /hal_espressif-2.7.6/examples/bluetooth/bluedroid/ble/gatt_security_server/ |
| D | README.md | 12 1.`esp_ble_gap_set_security_param` should be used to set the security parameters in the initial sta…
13 …iates the encryption, `esp_ble_gap_security_rsp` should be used to send security response to the p…
|
| /hal_espressif-2.7.6/examples/bluetooth/nimble/bleprph/main/ |
| D | Kconfig.projbuild | 39 prompt "MITM security"
41 Use this option to enable/disable MITM security.
|
| /hal_espressif-2.7.6/components/nvs_flash/ |
| D | README_CN.rst | 254 …的密钥存储于其他分区，并进行了 :doc:`flash 加密 <../../security/flash-encryption>`。因此，在使用 NVS 加密前应先启用 :doc:`flash 加…
273 使用 NVS 分区生成程序生成上述分区表，并烧录至设备。由于分区已标记为已加密，而且启用了 :doc:`flash 加密 <../../security/flash-encryption>`，引导程…
|
| /hal_espressif-2.7.6/docs/zh_CN/security/ |
| D | secure-boot-v1.rst | 1 .. include:: ../../en/security/secure-boot-v1.rst
|
