Bug#996978: libsrtp2-1: OpenSSL

2021-10-25 Thread Jonas Smedegaard
Quoting Alexander Traud (2021-10-25 13:06:00) > > the only real use back then [...] was for a random number function > > Sounds like I should have raised this before. Bugreports (and other kinds of reports - the name is kinda misleading) are always appreciated. > libSRTP required a crypto

Bug#996978: libsrtp2-1: OpenSSL

2021-10-25 Thread Alexander Traud
> the only real use back then [...] was for a random number function Sounds like I should have raised this before. libSRTP required a crypto library to support AES-GCM based crypto suites [1]. Actually, I use those suites via Digium Asterisk:

Bug#996978: libsrtp2-1: OpenSSL

2021-10-22 Thread Jonas Smedegaard
Hi Alexander, Quoting Alexander Traud (2021-10-21 21:42:10) > One year ago [1], you enabled NSS as crypto library. With that AES-GCM > and AES-NI are possible. However, libSRTP can be built with NSS or > OpenSSL. You played around with OpenSSL six years ago [2]. Do you > remember why it

Bug#996978: libsrtp2-1: OpenSSL

2021-10-21 Thread Alexander Traud
Package: libsrtp2-1 Version: 2.4.2-1 Severity: wishlist One year ago [1], you enabled NSS as crypto library. With that AES-GCM and AES-NI are possible. However, libSRTP can be built with NSS or OpenSSL. You played around with OpenSSL six years ago [2]. Do you remember why it failed? Curl has