this is more of a problem w/ the utility function being in lora
which loraserv imports...  if/when that happens this could be reverted..

This just makes sure things are a little tighter wrt protocol
compliance, ensuring that a corrupted initiator doesn't do bad
things..

This also adds a check to make sure that the allocated structure matches
the C code so that things won't break.

This breaks out the session state into it's own object... allowing a
common function to handle the state machine...

This also adds a new powerful testing tool.  It's a Synchronization
primitive that will ensure blocks of code run in the expected order,
and only run when the previous block has fully run...  This helps
ensure ordering between many tasks, to cause race conditions that
would otherwise be hard to cause..

are ignored, and it triggers a resent of the previous packet...

3-4 seconds to gather all this...  need to add a blinking light to this
so it's clear that it's still starting..

This is better than using RAM, as it keeps the state between power
cycles...

Also remind people that it's their responsiblity to follow licenses..

Turns out there's a bit of code that isn't compatible w/ the Python version,
eliminate it...  This was to support encoding lengths (via negative length
parameters)...

Also, the default C version (which we want to use) is Keccak(800) and not
Keccak(1600), switch Python to 800, as it'll be faster on the 32-bit uC, and
still has plenty of security margin...

The old method would introduce a race condition where the buffer
could be overwritten before the data was consumed.  For slow, single
character typing this was fine, but w/ packets being generated by
a computer, this would cause corruption of the incoming data..

custom one..

git-subtree-dir: loramac
git-subtree-split: 34f8c27281