Hello,
> The example is helpful, but it isn't clear to me when/how the DTLS
> session is established. In the _read function it appears that the
> session may be setup either during BIO_dgram_set_peer or SSL_set_bio.
In _read() session may be setup using BIO_dgram_set_peer() AND
SSL_set_bio().
Thi
The example is helpful, but it isn't clear to me when/how the DTLS
session is established. In the _read function it appears that the
session may be setup either during BIO_dgram_set_peer or SSL_set_bio.
Furthermore, it seems that the DTLS clienthello datagram is now sitting
in the memory buffer
Hello,
> Interesting,
> Two more questions.
>
> 1. Which callback should be used to perform a specific action after a
> DTLS session is setup. SSL_CTX_set_verify looks like a possibility. Is
> it called again when the the DTLS session is renegotiated?
If you want to write your own verification fun
Interesting,
Two more questions.
1. Which callback should be used to perform a specific action after a
DTLS session is setup. SSL_CTX_set_verify looks like a possibility. Is
it called again when the the DTLS session is renegotiated?
2. Can you offer any suggestions about how to de-multiplex multi
Hello,
> Can anyone tell me if the behavior of the BIO_new_accept, BIO_do_accept,
> and BIO_read functions changes in any way while using DTLS?
DTLS works over UDP so BIO_do_accept has no usage.
Internally DTLS works on BIO created with BIO_new_dgram() and uses
BIO_read() on that BIO (ssl3_read_n(
Hi All,
Can anyone tell me if the behavior of the BIO_new_accept, BIO_do_accept,
and BIO_read functions changes in any way while using DTLS?
Thanks,
Jeremy
__
OpenSSL Project http://www.opens
