-
Notifications
You must be signed in to change notification settings - Fork 4
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
STM32G0_Nucleo #3
base: main
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,142 @@ | |||
#MicroXplorer Configuration settings - do not modify |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
walfssl.ioc -> wolfssl.ioc?
|
||
#include <wolfssl/wolfcrypt/pwdbased.h> // For wc_PBKDF2_HMAC | ||
#include <wolfssl/wolfcrypt/aes.h> // For wc_AesSetKeyDirect | ||
#include <user_settings.h> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please move includes for settings.h and options.h above any other wolfSSL headers.
options.h is only generated if building the wolfSSL from ./configure or cmake. Your use-cases should be covered with including wolfssl/wolfcrypt/settings.h.
If you are not using the Cube MX HAL wolfSSL pack then make sure your project defines WOLFSSL_USER_SETTINGS.
See https://github.com/wolfSSL/wolfssl/blob/master/wolfssl/wolfcrypt/settings.h#L332
Hi @tecsantoshkumar thank you for your code contribution. Can you tell us a bit about your project and use-case? Is this for fun/school or for a company? Thanks, David Garske, wolfSSL |
/**
/ #ifdef __cplusplus /* Includes ------------------------------------------------------------------*/ /** /---------- WOLF_CONF_WOLFCRYPT_ONLY -----------/ /---------- WOLF_CONF_TLS13 -----------/ /---------- WOLF_CONF_TLS12 -----------/ /---------- WOLF_CONF_DTLS -----------/ /---------- WOLF_CONF_MATH -----------/ /---------- WOLF_CONF_RTOS -----------/ /---------- WOLF_CONF_RNG -----------/ /---------- WOLF_CONF_RSA -----------/ /---------- WOLF_CONF_ECC -----------/ /---------- WOLF_CONF_DH -----------/ /---------- WOLF_CONF_AESGCM -----------/ /---------- WOLF_CONF_AESCBC -----------/ /---------- WOLF_CONF_CHAPOLY -----------/ /---------- WOLF_CONF_EDCURVE25519 -----------/ /---------- WOLF_CONF_MD5 -----------/ /---------- WOLF_CONF_SHA1 -----------/ /---------- WOLF_CONF_SHA2_224 -----------/ /---------- WOLF_CONF_SHA2_256 -----------/ /---------- WOLF_CONF_SHA2_384 -----------/ /---------- WOLF_CONF_SHA2_512 -----------/ /---------- WOLF_CONF_SHA3 -----------/ /---------- WOLF_CONF_PSK -----------/ /---------- WOLF_CONF_PWDBASED -----------/ /---------- WOLF_CONF_KEEP_PEER_CERT -----------/ /---------- WOLF_CONF_BASE64_ENCODE -----------/ /---------- WOLF_CONF_OPENSSL_EXTRA -----------/ /---------- WOLF_CONF_TEST -----------/ /---------- WOLF_CONF_PQM4 -----------/ /* ------------------------------------------------------------------------- / #if defined(STM32WB55xx)
// #define HAL_CONSOLE_UART huart4
// #define WOLF_CRYPTO_CB /* ------------------------------------------------------------------------- / /* ------------------------------------------------------------------------- / /* ------------------------------------------------------------------------- /
/* ------------------------------------------------------------------------- / #if defined(WOLF_CONF_TLS13) && WOLF_CONF_TLS13 == 1 /* TLS Session Cache */ /* Post Quantum
/* ------------------------------------------------------------------------- /
#else /* ECC */
#endif /* DH / /* AES / #if defined(WOLF_CONF_AESCBC) && WOLF_CONF_AESCBC == 1 /* Other possible AES modes */ /* ChaCha20 / Poly1305 */
#endif /* Ed25519 / Curve25519 */
#endif /* ------------------------------------------------------------------------- / /* Sha2-256 /
#else /* Sha2-512 /
#endif /* Sha2-384 */ /* Sha3 */ /* MD5 / /* ------------------------------------------------------------------------- / /* ------------------------------------------------------------------------- /
#else /* ------------------------------------------------------------------------- / /* Override Current Time / /* ------------------------------------------------------------------------- / /* ------------------------------------------------------------------------- / #if defined(WOLF_CONF_TEST) && WOLF_CONF_TEST == 0 #define NO_FILESYSTEM #define NO_DSA /* In-lining of misc.c functions / /* Base16 / Base64 encoding */ /* bypass certificate date checking, due to lack of properly configured RTC source */ #ifdef __cplusplus /**
/*END OF FILE/ |
hello David Garske, |
Hi @tecsantoshkumar , For code contributions we require a signed contributor agreement. Can you email support at wolfssl dot com and reference this PR? Please provide information on the company and your location. Thanks, |
Hi @dgarske, I am Santosh Kumar from Delhi, India. I have previously worked with you on AES-128 and AES-256 CBC encryption for the JIO Vehicle Tracking Device project for EDS India. I successfully implemented encryption on the STM32G030T6 and STM32F091RC MCUs. Given this, I would like to merge the STM32F091RC implementation into the same project. Previously, you mentioned that this MCU was not supported. If possible, could you add support for both STM32G0 and STM32F0 to the project? Looking forward to your response. Best Regards, |
sure will update on support on wolfssl email |
Hi @tecsantoshkumar , did you send an email to our support alias? I couldn't find it. Looking forward to getting you setup as a contributor. |
@tecsantoshkumar? Awaiting your support email. Thank you |
Dear David Garske,
Thank you for reaching out. I will proceed with the required contributor
agreement.
I will email ***@***.***, referencing this PR, and provide the
necessary details. For your reference, my company details are as follows:
- *Company:* EDS-INDIA
- *Location:* Delhi, India
Please let me know if there are any additional requirements.
Best regards,
Santosh Kumar
…On Thu, 27 Feb 2025 at 04:47, David Garske ***@***.***> wrote:
Hi @tecsantoshkumar <https://github.com/tecsantoshkumar> ,
For code contributions we require a signed contributor agreement. Can you
email support at wolfssl dot com and reference this PR? Please provide
information on the company and your location.
Thanks, David Garske, wolfSSL
sure will update on support on wolfssl email
Hi @tecsantoshkumar <https://github.com/tecsantoshkumar> , did you send
an email to our support alias? I couldn't find it. Looking forward to
getting you setup as a contributor. Thanks, David Garske, wolfSSL
@tecsantoshkumar <https://github.com/tecsantoshkumar>? Awaiting your
support email. Thank you
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO53MLG6YO2XDYSKTRRRHXT2RZDSFAVCNFSM6AAAAABV4U6TF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBWGQZDEOJWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: dgarske]*dgarske* left a comment
(wolfSSL/wolfssl-examples-stm32#3)
<#3 (comment)>
Hi @tecsantoshkumar <https://github.com/tecsantoshkumar> ,
For code contributions we require a signed contributor agreement. Can you
email support at wolfssl dot com and reference this PR? Please provide
information on the company and your location.
Thanks, David Garske, wolfSSL
sure will update on support on wolfssl email
Hi @tecsantoshkumar <https://github.com/tecsantoshkumar> , did you send
an email to our support alias? I couldn't find it. Looking forward to
getting you setup as a contributor. Thanks, David Garske, wolfSSL
@tecsantoshkumar <https://github.com/tecsantoshkumar>? Awaiting your
support email. Thank you
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO53MLG6YO2XDYSKTRRRHXT2RZDSFAVCNFSM6AAAAABV4U6TF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBWGQZDEOJWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you! Tracking in ZD 19467 |
By the way @tecsantoshkumar there are a few items of feedback that are not resolved. Like the |
Hi, WOLFSSL Team,
I have created a pull request to merge the latest updates for the STM32G0_Nucleo project. The changes include the implementation of WolfSSL AES CBC encryption for key sizes 128, 192, and 256. Below are the details:
Changes Made:
Added support for AES CBC 128-bit, 192-bit, and 256-bit encryption using the WolfSSL library.
Updated relevant code modules for seamless integration with the STM32G0_Nucleo board.
Tested the encryption functionality for all key sizes to ensure accuracy and performance.
Request:
Kindly review the code changes and provide your feedback. If everything looks good, please approve and merge the pull request.
Link to Pull Request:
Please let me know if you need any additional details or if there are specific test scenarios, you’d like me to address.
Thank you for your time and support!
Best regards,
Tec Santosh Kumar