-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
how to manage hardware encryption modules #9314
Comments
Better interfacing in memory via ioctl, you really don't want using a character device for many obvious reasons. However, to my knowledge, I don't think there is any existing layer in that regards ; would be new to architect, new territory to explore. |
here has some demo: https://github.com/apache/nuttx-apps/tree/master/testing/crypto
I would suggest that you follow the crypto framework since many other components will base on the new crypto framework:
If you don't follow the crypto framework, you will lose all possible new feature. |
You can redefine crypto primitives and engine within mbedtls, however, it would require to adopt something like PSA Crypto API/Protocol within NuttX (from bottom to top and top to bottom). This is a very long road ahead to get there. Not a student or a single man project. Update: zephyr team seems to move into/toward that direction: |
Thank you for your valuable advice, have a happy life! |
@xiaotailang 超可愛的 , 我喜歡 , 你也一樣法語怎麼說吗 , that is just to make you aware of and comprehend the true underlaying complexity of such task and request. Meanwhile, for educational purpose using hardware primitives from kern to user space can be done using ioctl ; make your own personal The solution I give you is pretty straightforward and practical ; not optimal nor perfect but achievable within few weeks of puzzling. |
@mu578 @xiaotailang we will implement both alt and psa on top of /dev/crytpo |
@xiaoxiang781216 @mu578 Okay,Thank you again for your valuable advice. I plan to follow the suggestions you gave me and wish you a happy life。 |
@xiaoxiang781216 ok, @xiaotailang it will give you a hand on primitives and how to handle them ; this is not so easy to get ; then you come back on PSA-project opening (can't run away) with that understanding and clear mind. Chokchok. And please stop with your happy life wishes: that's weird. @xiaotailang to give you some language and idiom context : "Have a good or a happy life" in plain English usually means "get lost, I don't want to hear about you ever" ; it doesn't have a retained positive sense or meaning. Most cases, it is very rude, it is meant to hurt. |
Hello everyone, first of all, thank you to the community for your enthusiastic answers to my previous questions and for providing valuable advice. I have some hardware encryption modules, such as AES, RAS, etc., that I want to use in the NuttX system. However, I'm not sure how to manage these hardware encryption modules in the NuttX system. Through my research, I found a crypto directory under NuttX, which seems to be used for encryption-related purposes, but it only seems to implement various encryption algorithms in pure software. At the same time, I found that support for some hardware encryption modules, such as ESP32C3, was recently added to NuttX 12.1, but I couldn't find how to use these encryption modules at the application layer. I plan to manage each hardware encryption module through a character device. Is managing them through character devices feasible? Are there better ways to manage them in NuttX?
The text was updated successfully, but these errors were encountered: