On Wed, 10 Aug 2022 16:33:27 GMT, Daniel Jeliński wrote:
> > Could it be a TLS implementation problem that the server should not read
> > application data as handshaking data?
>
> Not really; `SSLEngine#unwrap` does not have to consume the entire
> ByteBuffer, and it's the application's respon
On Fri, 5 Aug 2022 12:25:36 GMT, Daniel Jeliński wrote:
> Fix `SSLEngineService` test class to make sure it does not discard any
> network data between `handshaking` and `receive`.
>
> With TLS1.3 the client starts sending application data immediately after
> sending the Finished message. The
On Wed, 10 Aug 2022 15:40:26 GMT, Xue-Lei Andrew Fan wrote:
> Could it be a TLS implementation problem that the server should not read
> application data as handshaking data?
Not really; `SSLEngine#unwrap` does not have to consume the entire ByteBuffer,
and it's the application's responsibilit
On Fri, 5 Aug 2022 12:25:36 GMT, Daniel Jeliński wrote:
> Fix `SSLEngineService` test class to make sure it does not discard any
> network data between `handshaking` and `receive`.
>
> With TLS1.3 the client starts sending application data immediately after
> sending the Finished message. The
On Fri, 5 Aug 2022 12:25:36 GMT, Daniel Jeliński wrote:
> Fix `SSLEngineService` test class to make sure it does not discard any
> network data between `handshaking` and `receive`.
>
> With TLS1.3 the client starts sending application data immediately after
> sending the Finished message. The
Fix `SSLEngineService` test class to make sure it does not discard any network
data between `handshaking` and `receive`.
With TLS1.3 the client starts sending application data immediately after
sending the Finished message. The server may read some of that data in the
`handshaking` method. This
