Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make Secure Element Available for all chips (IDFGH-13922) #14761

Open
javoerro opened this issue Oct 21, 2024 · 1 comment
Open

Make Secure Element Available for all chips (IDFGH-13922) #14761

javoerro opened this issue Oct 21, 2024 · 1 comment
Assignees
@nileshkale123
Labels
Status: Opened Issue is new Type: Feature Request Feature request for IDF

Comments

@javoerro
Copy link

Is your feature request related to a problem?

Why is CONFIG_ESP_TLS_USE_SECURE_ELEMENT not available for chips other than ESP32? I need to know the reason in order to find a workaround.

Describe the solution you'd like.

Just not make the option dependable of IDF_TARGET_ESP32

Describe alternatives you've considered.

I dont want to use an edited and unofficial version of IDF.

Additional context.

No response
@javoerro javoerro added the Type: Feature Request Feature request for IDF label Oct 21, 2024
@espressif-bot espressif-bot added the Status: Opened Issue is new label Oct 21, 2024
@github-actions github-actions bot changed the title Make Secure Element Available for all chips Make Secure Element Available for all chips (IDFGH-13922) Oct 21, 2024
@cristianfunes79
Copy link
Contributor

It seems this feature was discussed a few months ago: http://esp32.io/viewtopic.php?t=33481
I can start working on this feature.

@cristianfunes79 cristianfunes79 mentioned this issue Oct 25, 2024
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nileshkale123 nileshkale123

Labels
Status: Opened Issue is new Type: Feature Request Feature request for IDF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cristianfunes79 @espressif-bot @javoerro @nileshkale123