Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Tea looks to be quite simple and will probably do what you need.</p> <p>I added a tea example to my thumbulator project at github (thumb instruction set simulator, cortex-m3 style boot).</p> <p>compiling for thumb with -O2 or similar optimizations:</p> <p>arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2011.03-41) 4.5.2 encrypt 136 bytes decrypt 128 bytes</p> <p>llvm 29 encrypt 92 bytes decrypt 96 bytes</p> <p>compiling for generic arm...</p> <p>gnu encrypt 188 bytes, decrypt 184 bytes llvm encrypt 112 bytes, decrypt 116 bytes</p> <p>For authentication, is there a one to one relationship between the ip address table and the number of devices? Basically does there need to be more than one unique identifier per device? Are you wanting the other side that is making the connection to the embedded system to log in in some form or fashion? Or are you controlling the binaries/code on both ends and there are no users or no selection of devices (the programs know what to do), etc? If each device has a known ip address, that ip address could be the key to the encryption (plus other bytes common to all or derived in some fashion that everyone knows) If a connection coming in is 1) not from the approved list 2) encryption fails when the embedded systems ip address based key fails then reject the connection.</p> <p>Your security can only go so far anyway, if you need something really robust you probably need more horsepower in the embedded system and then implement one of the common/standard systems like ssl.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload