-
Notifications
You must be signed in to change notification settings - Fork 635
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
Fleet provisioning library compilation issues #1807
Comments
Hi @manav-eheat, |
@manav-eheat : For Espressif platforms, we recommend using the esp-aws-iot component which contains many of the same libraries used in this repository. You may also reference our esp32c3 reference integration for some setup guidance. Most of it should be applicable to other SoCs from Espressif. Regarding fleet provisioning, the most applicable reference for you is probably our Windows Simulator Fleet Provisioning Demo which is explained on this page. Newer SoCs from Espressif have a Digital Signature peripheral, meant for storing private keys. This is preferable to storing keys in NVS or SPIFFS. corePKCS11 does not have a DS peripheral backend available, so the customer will need to replace the relevant pkcs11 api calls for private key operations with the relevant call to the espressif ds api. For certificate storage, you might consider enabling the espressif Virtual Filesystem and SPIFFS components and replacing pkcs11 certificate calls with mbedtls native functions like mbedtls_x509_crt_parse_file or using functions like mbedtls_x509_crt_parse_der with the NVS module. If a DS peripheral is not available on your platform, you may also store private keys in flash. We recommend that customers always encrypt private keys at rest. |
Hi Jason,
We were getting following errors due to some missing packages. Can you please provide the pointer for complete built up Fleet Provisioning libraries for Embedded C for ESP 32 platform.
Thanks,
Manav
�
�
From: jasonpcarroll ***@***.***>
Sent: Tuesday, June 21, 2022 9:00 PM
To: aws/aws-iot-device-sdk-embedded-C ***@***.***>
Cc: manav-eheat ***@***.***>; Mention ***@***.***>
Subject: Re: [aws/aws-iot-device-sdk-embedded-C] Fleet provisioning library compilation issues (Issue #1807)
�
Hi @manav-eheat <https://github.com/manav-eheat> ,
Sorry for the late reply. I do not see your attached logs. If you could please re-attach or just past them here - I will look into this issue.
Best,
Jason Carroll
—
Reply to this email directly, view it on GitHub <#1807 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQU4UYFFADBXZL4JH43DO7DVQHNXJANCNFSM5YYVLRZQ> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQU4UYDDN2FNS5DJNZYAK53VQHNXJA5CNFSM5YYVLRZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIVAXNJQ.gif> Message ID: ***@***.*** ***@***.***> >
|
We are trying to implement the Fleet provisioning using the following reference
https://github.com/aws/aws-iot-device-sdk-embedded-C/tree/main/demos/fleet_provisioning/fleet_provisioning_with_csr
We are facing many compilation errors (attached). Please help providing the package and libraries which are built completely for Fleet provisioning for embedded-C SDK.
thanks,
eHeat
The text was updated successfully, but these errors were encountered: