Hello!
On Wed, Sep 04, 2019 at 09:25:57AM -0400, Phillip Odam wrote:
[...]
> Also, the following reference was provided providing a basis for the TLS
> handshake requirement, sections 7.2.1 and 7.2.2 -
> https://tools.ietf.org/html/rfc5246#section-7.2.1. Admittedly production
> implementation
Hi Maxim
Thanks for the prompt feedback. My understanding for requiring the TLS
itself to fail, as opposed to doing exactly what you described which is
also exactly what we've done for other endponts... I quite like nginx's
ability here, is that it prevents being able to take advantage of
exp
Hello!
On Wed, Sep 04, 2019 at 08:35:05AM -0400, Phillip Odam wrote:
> Hi,
>
> I tried asking the following on the general mailing list but I'm
> guessing this is tending more towards development.
>
> I have a project that involves mutual / two way TLS and one of the
> requirements is that th
Hi,
I tried asking the following on the general mailing list but I'm
guessing this is tending more towards development.
I have a project that involves mutual / two way TLS and one of the
requirements is that the TLS handshake must fail ie. be terminated
before completion if the handshake is
