Yes just means an RFC is on the standards track. Not TLS.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
The table in the following section of the latest draft for TLS 1.3 started
the confusion:
https://tools.ietf.org/html/draft-ietf-tls-tls13-11#section-11
On Sun, Jan 24, 2016 at 6:03 PM, Salz, Rich wrote:
> > Really? Strange. They are recommended for TLS 1.3
>
> No they're not.
>
> Start perha
> Really? Strange. They are recommended for TLS 1.3
No they're not.
Start perhaps at this thread:
https://www.ietf.org/mail-archive/web/tls/current/msg12283.html
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/ope
Really? Strange. They are recommended for TLS 1.3
On Sun, Jan 24, 2016 at 5:17 PM, Salz, Rich wrote:
> Like I said, I don't know that you can do it without changing some
> source. And also, heartbeats for TLS (and maybe DTLS) are going away in
> the next release.
>
> ___
Like I said, I don't know that you can do it without changing some source. And
also, heartbeats for TLS (and maybe DTLS) are going away in the next release.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-d
I was hoping SSL_peek might work, but I can't find any documentation.
I do have the guarantee from the application layer that messaging occurs in
a strict client request -> server response sequence, without any
pipelining, etc. I know with certainty that the heartbeat response is the
next record
I don't think you can do this. You will have to have your layer wrap
application data in its own packaging layer. And of course, if there's a TCP
break, you have no idea how many bytes were sent/received on either end.
___
openssl-dev mailing list
To
It's for research.
I need a way, using only SSL layer functionality, for a client to know with
certainty that the server has received a message. This is trivial at the
application layer, but that is not what is wanted.
In particular, the client needs to know that the server has completed a
resume
TLS does this automatically with its record layer and MAC's. Why do you need
to repeat it?
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Is it possible to check for a heartbeat response without calling SSL_read?
I'm pretty sure the answer is no.
This is problematic for me. I'm trying to make a library layer on top of
OpenSSL that uses the heartbeat as an authenticated ack of earlier
messages, without changing the application layer
10 matches
Mail list logo
