Hi Jan,
Thanks for responding :-)
When I started this project I found (the hard way) that PolarSSL uses memory
allocations, and lots of it.
As my system is complicated I cannot spare any of the 192Kb of the micro .
The micro has a second bank that is fast memory (CCM) so I used this one. I
hav
Hi Jan,
Let me see if I understand you... MAX_CONTENT_LEN is defined in my system to
the default 16K.
I have 64K of RAM available just for the SSL use.
So memory limits are not at SSL layer, I think.
The SSL layer is reading a record and then the data. Data is read into its own
buffers.
Hi Noam!
SSL/TLS isn't that simple. Besides encryption the data is also hashed
to detect data integrity issues. This places strong resource
requirements on the block size that is used for hashing and this is
where MAX_CONTENT_LEN comes into play: mbedtls needs/reserves two
buffers of that s
Hi Simon,
Yes it may be an issue, any ideas or a change in the settings I placed here
earlier ?
What I am puzzled about is that SSL/TLS transfer a key over RSA. Once the key
has been
transferred (SSL handshake) the encryption/decryption are symmetric. Either
using AES, DES etc..
So if one
I did have mbedTLS running against our httpd (no sockets) but the
resource usage was rather high.
I'd imagine the problem could be lwIP's memory configurations here, too.
Simon
Jan Menzel wrote:
Hi Noam!
I've designed a system with almost the same setup which works well
since a few ye
Hi Noam!
I've designed a system with almost the same setup which works well
since a few years incl. firmware updates of a ~200kb.
Did you checked the memory consumption of the ip stack and the ssl max
content length setting? The default max content length setting is IIRC
16kb, which
Noam Weissman wrote:
> I have a client, single task using the socket API using and also PolarSSL for
> SSL support.
> [..]
> When I try to send small messages from the server to my client all is working
> ok but when I try to push a large
> message 6K and up my ssl_read function fails with a read
Hi,
I have a client, single task using the socket API using and also PolarSSL for
SSL support.
The client is WebSocket client and all seems to work ok.
When I try to send small messages from the server to my client all is working
ok but when I try to push a large
message 6K and up my ssl_read
