Hi, Currently there are 2 crypto libraries in mynewt sourcetree - TinyCrypt and mbedTLS. TinyCrypt is used only by Bluetooth LE Secure Connections and bootutils.
>From a very brief look it seems that mbetTLS provides necessary EC and DH API. Also TinyCrypt seems to be in quite old version 1.0 while 2.0.5 is already available. (I'm not sure about mbetTLS version). Having two crypto libraries being used together seems like a waste of memory. What are the plans for this? Adding generic crypto API that would allow to choose backend on compilation? Remove one of the libraries and rewrite code that is using it to other crypto? Just leave both around and use them where it seems better? If last option is feasible IMO at least Mynewt Core should rely on single crypto lib while applications can choose any of those if needed. Comments? -- pozdrawiam Szymon Janc
