Re: LibreSSL: is there any reason to keep opaque_prf_input?

2014-06-12 Thread Miod Vallat
> Miod Vallat writes: > > > You're right. What about the following diff? (major bump for libssl) > > Looks OK to me. There's also a few tendrils in regress: Indeed. Applied, thanks!

Re: LibreSSL: is there any reason to keep opaque_prf_input?

2014-06-10 Thread Brendan MacDonell
Miod Vallat writes: > You're right. What about the following diff? (major bump for libssl) Looks OK to me. There's also a few tendrils in regress: Index: ssl/ssltest.c === RCS file: /home/cvsync/openbsd/src/regress/lib/libssl/ssl/

Re: LibreSSL: is there any reason to keep opaque_prf_input?

2014-06-09 Thread Miod Vallat
> Hello, > > I just noticed r1.44 to t1_lib.c. I'm not sure that auditing > opaque_prf_input is a good use of anyone's time -- I think it might be > better to just run "unifdef -U TLSEXT_TYPE_opaque_prf_input" and be done > with it. > > Here's the history of opaque_prf_input as I understand it: >

LibreSSL: is there any reason to keep opaque_prf_input?

2014-06-04 Thread Brendan MacDonell
Hello, I just noticed r1.44 to t1_lib.c. I'm not sure that auditing opaque_prf_input is a good use of anyone's time -- I think it might be better to just run "unifdef -U TLSEXT_TYPE_opaque_prf_input" and be done with it. Here's the history of opaque_prf_input as I understand it: - In 2006, the D