[rtmpdump] [PATCH] Add support for building with gnutls with nettle as backend
Martin Storsjö
martin at martin.st
Mon Feb 27 09:49:22 CET 2012
On Sun, 26 Feb 2012, Howard Chu wrote:
> Since gcrypt is an utter disaster, and gnutls is using nettle as the default
> backend now, we could just use nettle and drop gcrypt.
Yes, that's also totally ok with me.
As I wrote earlier, this is still missing some verification of the swfhash
codepaths, I think I've got the rest of it tested already. Once someone
with access to test urls that actually require the swfhash stuff has
verified it, please go ahead.
> Of course, gnutls itself is also an utter disaster, with API/ABI
> compatibility breakages every few months. I really don't see the value in
> supporting gnutls any further at all. If you want a comprehensive crypto
> library that works, use OpenSSL. If you want a GPL'd crypto library that
> works, use PolarSSL. We don't need to support every flavor-of-the-month
> science project, we only need to support code that's actually usable.
I'd still vote for keeping it - for many of my use cases, GPL isn't an
option.
// Martin
More information about the rtmpdump
mailing list