[14850] in cryptography@c2.net mail archive
RE: Open Source Embedded SSL - (License and Memory)
daemon@ATHENA.MIT.EDU (Peter Gutmann)
Fri Dec 5 13:51:01 2003
X-Original-To: cryptography@metzdowd.com
X-Original-To: cryptography@metzdowd.com
Date: Fri, 5 Dec 2003 14:15:36 +1300
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: billtlists@icarion.com, jsec@peersec.com
Cc: cryptography@metzdowd.com
"J Harper" <jsec@peersec.com> writes:
>>2) Make it functional on systems without memory allocation. Did I
>>mention that I work on (very) small embedded systems? Having fixed
>>spaces for variables is useful when you want something to run
>>deterministically for a long time with no resets, and I have yet to
>>find a free bignum library that didn't want to use malloc all the
>>time.
>
>We have implemented a block allocation scheme for our device Web services
>product that would probably solve this issue. Queues of various structure
>sizes are held within a single chunk of memory.
How common is it to find an embedded system sophisticated enough to have a TCP
stack and ethernet interface (and running SSL), but not sophisticated enough
to have a malloc() implementation? I've always assumed that anything with the
former will also have the latter (I know there are some highly constrained
embedded platforms used in some web-enabled widgets, but they usually don't
run SSL). My code will run without malloc() in general, but assumes that if
you have a TCP stack and ethernet then you're also going to have malloc()
support. For the non-malloc platforms, it's written to grab memory in a FIFO
manner, so you can get away with a simple brk-style allocator.
Peter.
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
