-
Notifications
You must be signed in to change notification settings - Fork 21
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
TLSScoket issue in Nuvoton-IoTM487 #46
Comments
@parthibanNVS This issue has an incomplete or old issue template.For future reference please use an up to date clone of the repository before raising issues. Many thanks. |
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. |
Hi @parthibanNVS, TLS requires an entropy source, usually TRNG (true random number generator), in order to transfer data securely. But NUMAKER_IOT_M487 doesn't have it, see discussion in ARMmbed/mbed-os#11680, so TLSSocket and the Mbed TLS functionalities it depends on can't be enabled. An alternative option is to add an NV seed support, useful for targets without TRNG. See this documentation for how to do this. |
Thanks for the reply. I will check this.
…On Wed, Jun 23, 2021 at 5:37 PM Lingkai Dong ***@***.***> wrote:
Hi @parthibanNVS <https://github.com/parthibanNVS>,
TLS requires an entropy source, usually TRNG (true random number
generator), in order to transfer data securely. But NUMAKER_IOT_M487
doesn't have it, see discussion in ARMmbed/mbed-os#11680
<ARMmbed/mbed-os#11680>, so TLSSocket and the
Mbed TLS functionalities it depends on can't be enabled.
An alternative option is to add an NV seed support, useful for targets
without TRNG. See this documentation
<https://os.mbed.com/docs/mbed-os/v6.11/porting/entropy-sources.html#how-to-implement-the-non-volatile-seed-entropy-source>
for how to do this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS2VMXL2JNFPS5ASENZMGSLTUHFB5ANCNFSM46QX7G7Q>
.
--
Parthiban Kandasamy
Technical Manager
9790329795
HFS Groups
|
Hi, this project i configured it for IoT-M487 kit from nuvoton in mbedapp.json but is throwing error for tlssocket as shown below
**"Compile [ 1.9%]: AWSClient.cpp
[Error] AWSClient.h@52,5: unknown type name 'TLSSocket'; did you mean 'TCPSocket'?
[Error] AWSClient.cpp@271,28: undeclared identifier 'TLSSocket' in destructor name
[Error] AWSClient.cpp@272,34: unknown type name 'TLSSocket'; did you mean 'TCPSocket'?
[Error] AWSClient.cpp@275,27: no member named 'set_hostname' in 'TCPSocket'
[Error] AWSClient.cpp@278,27: no member named 'set_client_cert_key' in 'TCPSocket'
[Error] AWSClient.cpp@284,27: no member named 'set_ca_chain' in 'TCPSocket'
[ERROR] In file included from .\mbed-client-for-aws\source\AWSClient.cpp:26:
./mbed-client-for-aws/include/AWSClient\AWSClient.h:52:5: error: unknown type name 'TLSSocket'; did you mean 'TCPSocket'?
TLSSocket socket;
^~~~~~~~~
TCPSocket
./mbed-os/connectivity/netsocket/include\netsocket/TCPSocket.h:33:7: note: 'TCPSocket' declared here
class TCPSocket : public InternetSocket {
^
.\mbed-client-for-aws\source\AWSClient.cpp:271:28: error: undeclared identifier 'TLSSocket' in destructor name
networkContext.socket.~TLSSocket();
^~~~~~~~~
TCPSocket
.\mbed-client-for-aws\source\AWSClient.cpp:272:34: error: unknown type name 'TLSSocket'; did you mean 'TCPSocket'?
new (&networkContext.socket) TLSSocket();
^~~~~~~~~
TCPSocket
./mbed-os/connectivity/netsocket/include\netsocket/TCPSocket.h:33:7: note: 'TCPSocket' declared here
class TCPSocket : public InternetSocket {
^
.\mbed-client-for-aws\source\AWSClient.cpp:275:27: error: no member named 'set_hostname' in 'TCPSocket'
networkContext.socket.set_hostname(hostname);
The text was updated successfully, but these errors were encountered: