Hi yangyh12138 ,
in the blog post it says:
We can help with:
+ Technical guidance on security implementation
+ Pre-filled compliance documentation templates from the platform perspective
Is the pre-filled compliance documentation template already available and if yes can you tell us where to ...
Search found 17 matches
- Wed Jun 18, 2025 10:02 am
- Forum: ESP-IDF
- Topic: Question about RED DA Certification Compliance
- Replies: 1
- Views: 239
- Tue Jun 10, 2025 1:47 pm
- Forum: ESP-IDF
- Topic: Using gpio_ll_set_level in call_start_cpu0 in bootloader_start.c
- Replies: 2
- Views: 100
Re: Using gpio_ll_set_level in call_start_cpu0 in bootloader_start.c
Thank you, adding "hal" to required components in the component's CMakeLists.txt worked.
- Mon Jun 02, 2025 8:29 am
- Forum: ESP-IDF
- Topic: Using gpio_ll_set_level in call_start_cpu0 in bootloader_start.c
- Replies: 2
- Views: 100
Using gpio_ll_set_level in call_start_cpu0 in bootloader_start.c
Hi,
I'm porting a project from IDF 4.x to 5.x and need to call
esp_rom_gpio_pad_select_gpio(PIN_LED);
gpio_ll_input_disable(&GPIO, PIN_LED);
gpio_ll_output_enable(&GPIO, PIN_LED);
gpio_ll_set_level(&GPIO, PIN_LED, 0);
in call_start_cpu0() in
bootloader_components/main/bootloader_start.c
My ...
I'm porting a project from IDF 4.x to 5.x and need to call
esp_rom_gpio_pad_select_gpio(PIN_LED);
gpio_ll_input_disable(&GPIO, PIN_LED);
gpio_ll_output_enable(&GPIO, PIN_LED);
gpio_ll_set_level(&GPIO, PIN_LED, 0);
in call_start_cpu0() in
bootloader_components/main/bootloader_start.c
My ...
- Mon Jul 22, 2024 10:31 am
- Forum: ESP-IDF
- Topic: Bluetooth NimBLE security: Allow connection only after pressing button
- Replies: 4
- Views: 3031
Re: Bluetooth NimBLE security: Allow connection only after pressing button
The problem with this approach is, that some devices for example an iPhone are changing their bluetooth device address every 30 minutes. So whitlisting specific device addresses will not work with iPhones and other client devices.
- Thu Jul 18, 2024 11:36 am
- Forum: ESP-IDF
- Topic: Bluetooth NimBLE security: Allow connection only after pressing button
- Replies: 4
- Views: 3031
Re: Bluetooth NimBLE security: Allow connection only after pressing button
>You can opt for limited discovery , where advertising is done only for limited period of time. After that advertising stops, so remote devices cannot find your device or initiate connection.
The problem when opting in for limited discovery the ESP32 will only be visible for 30 seconds and after ...
The problem when opting in for limited discovery the ESP32 will only be visible for 30 seconds and after ...
- Tue Jul 16, 2024 11:23 am
- Forum: ESP-IDF
- Topic: More secure Bluetooth LE pairing method
- Replies: 19
- Views: 11439
Re: More secure Bluetooth LE pairing method
Ok, i found a way to restrict access to characteristics only for paired devices:
You have to set the characteristics flags to:
BLE_GATT_CHR_F_WRITE | BLE_GATT_CHR_F_WRITE_ENC
(you have to use BOTH to make it work)
One Question still remains:
You said that you allow every device to connect to you ...
You have to set the characteristics flags to:
BLE_GATT_CHR_F_WRITE | BLE_GATT_CHR_F_WRITE_ENC
(you have to use BOTH to make it work)
One Question still remains:
You said that you allow every device to connect to you ...
- Mon Jul 15, 2024 9:57 am
- Forum: ESP-IDF
- Topic: More secure Bluetooth LE pairing method
- Replies: 19
- Views: 11439
Re: More secure Bluetooth LE pairing method
I've configured ble_hs_cfg with your settings, and now I'm asked to enter a PIN when I'm training to bond with the ESP32-S3.
BUT the strange thing is, I'm still able to connect to the ESP32-S3 (without bonding) and I can use the Service-Characteristics (read/write values) of the ESP32-S3 through ...
BUT the strange thing is, I'm still able to connect to the ESP32-S3 (without bonding) and I can use the Service-Characteristics (read/write values) of the ESP32-S3 through ...
- Fri Jul 12, 2024 8:40 am
- Forum: ESP-IDF
- Topic: More secure Bluetooth LE pairing method
- Replies: 19
- Views: 11439
Re: More secure Bluetooth LE pairing method
Thanks I've tried bonding with the ESP32-S3 using the
https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-mobile
app.
The app shows that the ESP32-S3 was bonded, but the output of ESP32-S3 sill shows bonded=0:
I (173106) NimBLE: connection established; status=0
I (173106) NimBLE ...
https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-mobile
app.
The app shows that the ESP32-S3 was bonded, but the output of ESP32-S3 sill shows bonded=0:
I (173106) NimBLE: connection established; status=0
I (173106) NimBLE ...
- Fri Jul 12, 2024 7:07 am
- Forum: ESP-IDF
- Topic: More secure Bluetooth LE pairing method
- Replies: 19
- Views: 11439
Re: More secure Bluetooth LE pairing method
Good to hear that storing bonding in NVS is already working.
I don't want to disable bluetooth completely as it should be available for an already bonded device at any time.
It should not be possible for any other device to connect to the ESP32-S3 without pressing the pairing-button first.
An ...
I don't want to disable bluetooth completely as it should be available for an already bonded device at any time.
It should not be possible for any other device to connect to the ESP32-S3 without pressing the pairing-button first.
An ...
- Fri Jul 12, 2024 6:25 am
- Forum: ESP-IDF
- Topic: More secure Bluetooth LE pairing method
- Replies: 19
- Views: 11439
Re: More secure Bluetooth LE pairing method
Thank you, eriksl, that makes a lot of sense!
So wouldn't it be possible to allow pairing only for 30 seconds when pressing a button? So that a 5 digit pin would be secure enough if you only have 30 seconds to pair?
An once a device is paired, you disable pairing except when you press the button ...
So wouldn't it be possible to allow pairing only for 30 seconds when pressing a button? So that a 5 digit pin would be secure enough if you only have 30 seconds to pair?
An once a device is paired, you disable pairing except when you press the button ...