Hello,
> It seems the OpenSSL TLS server, when forced to use TLSv1,
> shuts down the connection immediately after receiving a
> ClientHello with major version number not equal to 0x03.
> Nothing was sent to the client to notify the error.
>
> >>> What could be sent
Marek Marcola wrote:
> Hello,
>
It seems the OpenSSL TLS server, when forced to use TLSv1,
shuts down the connection immediately after receiving a
ClientHello with major version number not equal to 0x03.
Nothing was sent to the client to notify the error.
>>> Wh
Hello,
> > > It seems the OpenSSL TLS server, when forced to use TLSv1,
> > > shuts down the connection immediately after receiving a
> > > ClientHello with major version number not equal to 0x03.
> > > Nothing was sent to the client to notify the error.
> >
> > What could be sent to the client to
Hello,
> > It seems the OpenSSL TLS server, when forced to use TLSv1,
> > shuts down the connection immediately after receiving a
> > ClientHello with major version number not equal to 0x03.
> > Nothing was sent to the client to notify the error.
>
> What could be sent to the client to notify it o
> It seems the OpenSSL TLS server, when forced to use TLSv1,
> shuts down the connection immediately after receiving a
> ClientHello with major version number not equal to 0x03.
> Nothing was sent to the client to notify the error.
What could be sent to the client to notify it of the error? Sinc
Hello,
> It seems the OpenSSL TLS server, when forced to use TLSv1, shuts down
> the connection immediately after receiving a ClientHello with major
> version number not equal to 0x03. Nothing was sent to the client to
> notify the error. I am wondering if there is a reason why an alert
> protocol
It seems the OpenSSL TLS server, when forced to use TLSv1, shuts down
the connection immediately after receiving a ClientHello with major
version number not equal to 0x03. Nothing was sent to the client to
notify the error. I am wondering if there is a reason why an alert
protocol message was not s
