[En-Nut-Discussion] include/crypto/bigint.h vs ./include/contrib/crypto/bigint.h
ole.reinhardt at embedded-it.de
Fri Apr 25 11:18:37 CEST 2014
Am 25.04.2014 10:59, schrieb Uwe Bonnes:
> Ole> These are two totally different libraries. The one from Daniel Otte
> Ole> (GPL), which now lives in nut/contrib/arm-crypto-lib, and the axTLS
> Ole> library (BSD), which lives int nut/crypto and nut/tls.
> For totally different things or for teh same thing done differently. Is
> there any need or profite to keep both?
The library, I added provides full TLS support for client and server. It
comes with its own crypto library and is BSD licensed, so fit ideally
into the Nut/OS environment. An HTTPS client demo was added to the
sample apps (nut/app/tls_client).
The arm-crypto-library is GPL code, but provides far more cryptographic
routines, than the TLS library. Sure, some of them are doubled though.
But as it is GPL code, you can not use it together with the TLS library,
as long as you won't put your whole code under GPL.
I see the profit to keep both in the fact, that the user can select,
which code to use for its own best purpose. So we should fix the include
path issue, but then let the selection up to the user.
To have both libraries won't make your code a single byte larger, as
long as you don't link to them.
kernel concepts GmbH Tel: +49-271-771091-14
Sieghuetter Hauptweg 48 Mob: +49-177-7420433
More information about the En-Nut-Discussion