Both solutions work, thanks!
-Original Message-
From: Matt Caswell
Sent: Thursday, 10 March 2022 13:51
To: Tal Dery ; openssl-users@openssl.org
Subject: Re: SSL_TLSEXT_ERR_NOACK not working as expected
On 10/03/2022 11:33, Tal Dery wrote:
> I am developing a MITM proxy ser
-users@openssl.org
Subject: Re: SSL_TLSEXT_ERR_NOACK not working as expected
On 10/03/2022 11:21, Tal Dery wrote:
Hi Matt,
Yes, I want to abort the session without notifying the client.
SSL_TLSEXT_ERR_ALERT_FATAL sent " 15 03 03 00 02 02 00" to client.
What can I do to not send the message?
: Thursday, 10 March 2022 13:25
To: Tal Dery ; openssl-users@openssl.org
Subject: Re: SSL_TLSEXT_ERR_NOACK not working as expected
On 10/03/2022 11:21, Tal Dery wrote:
> Hi Matt,
> Yes, I want to abort the session without notifying the client.
> SSL_TLSEXT_ERR_ALERT_FATAL sent " 15 03
That would be
a protocol violation. Don't do that.
Matt
Thanks
-Original Message-
From: Matt Caswell
Sent: Thursday, 10 March 2022 12:54
To: Tal Dery ; openssl-users@openssl.org
Subject: Re: SSL_TLSEXT_ERR_NOACK not working as expected
On 10/03/2022 10:26, Tal Dery wrote:
Hi,
I am im
; openssl-users@openssl.org
Subject: Re: SSL_TLSEXT_ERR_NOACK not working as expected
On 10/03/2022 10:26, Tal Dery wrote:
> Hi,
>
> I am implementing an SSL server.
>
> Using SSL_CTX_set_tlsext_servername_callback I'm checking the SNI.
>
> When SNI meets my requirement
On 10/03/2022 10:26, Tal Dery wrote:
Hi,
I am implementing an SSL server.
Using SSL_CTX_set_tlsext_servername_callback I'm checking the SNI.
When SNI meets my requirements (for example does not contain offensive
words) I allow the handshake by returning SSL_TLSEXT_ERR_OK.
When there is
Hi,
I am implementing an SSL server.
Using SSL_CTX_set_tlsext_servername_callback I'm checking the SNI.
When SNI meets my requirements (for example does not contain offensive words) I
allow the handshake by returning SSL_TLSEXT_ERR_OK.
When there is an offensive word, I do not want to send
