On Fri, Dec 21, 2018 at 11:20:43AM -0500, Viktor Dukhovni wrote:
> Which naturally does not map to any kind of certificate. While TLS
> 1.2 still lives and is still capable of aNULL ciphersuites, it might
> make sense to add a line of code to detect that condition, and not
> push anything onto th
On Fri, Dec 21, 2018 at 02:24:18PM +, Jeremy Harris wrote:
> > You provide much too little detail. This particular "error"
> > happens when a TLS 1.2 ciphersuite does not correspond to any
> > any public key type for which OpenSSL might have a certificate.
>
> A packet capture showed me the
I'm trying to understand how the generation of ASM-files
are done on x64. (I have no problems on x86).
With the generated Nmake makefile from a
perl Configure VC-WIN64A-ONECORE
when doing a:
nmake crypto\aes\libcrypto-lib-aesni-x86_64.obj
seems to do this:
set ASM=nasm
"f:/util/Strawber
On 21/12/2018 00:02, Viktor Dukhovni wrote:
>> Thanks for the hint. You are correct, and a clear before that set
>> of crypto operations gets me a far more reasonable message.
>
> Makes sense.
>
>> The error seems to be left around after SSL_accept(), and yet
>> it does not appear in my SNI callb
