PolarSSL

[jaromil]

Have you evaluated use of PolarSSL instead of OpenSSL?

It implements almost all the same calls, works better on embedded and is less license encumbered. It already can absolve to all tasks needed by OpenVPN, for instance.

Picocoin is neat! and much needed. will have a look...

[jgarzik]

Not familiar with PolarSSL, but always open to new ideas.

[jgarzik]

Bitcoin requires: sha1, sha256, ripemd160, BIGNUM, ECDSA.

Looks like PolarSSL lacks ECDSA and RIPEMD160, but has SHA1, SHA256 and BIGNUM.

[jaromil]

mmm... ECDSA secp256k1 is the tough guy.

[cjdelisle]

Possibly this could be used in conjunction: https://github.com/sipa/secp256k1
I would be concerned about the OpenSSL DER flexability issue, although I gather it's pretty well understood by now.

[ghost]

The current release of PolarSSL is 1.3.2 (Nov. 5th, 2013).

ECDSA has been supported since version 1.3.0:

https://polarssl.org/tech-updates/blog/new-features-in-polarssl-1.3.0

As far as I can see RIPEMD-160 is currently not supported but the main developer Paul Bakker is open to including it in the core code:

https://polarssl.org/discussions/feature-request/support-for-ripmed-algorithm

I have raised this as an issue on the PolarSSL github page:

Mbed-TLS/mbedtls#44

[ghost]

This is promising:

Mbed-TLS/mbedtls#44 (comment)

[pjbakker]

Added to the PolarSSL development branch (Both RIPEMD-160 and the Koblitz curves!)! So ready for testing.

Will be included in the release 1.3.4 that will show up after the weekend!

[pjbakker]

PolarSSL 1.3.4 is out with RIPEMD-160 and secp256k1 support.. Let me know if you run into anything!

[jgarzik]

Closing - moving in the direction of OpenSSL removal + algorithm direct inclusion

[jacobbogers]

jgarzik, this means you will "ripp" out specific OpenSSL functionality and add it to picocoin? as not to depend on the entire OpenSSL library?