Rich Salz wrote:
openSSL 0.9.8 comes with support for DTLS, which is TLS over UDP.
Another point for the original poster to keep in mind is that SSL/TLS can
require multiple read/writes for a single application-level packet
exchange. This isn't always obvious to folks starting out. I think the
DTLS spec discusses some of the implications.
You might also want to look at the "security" in SNMPv3.
/r$
Thank you for all the replies.
I'll grab the opportunity here to point out that I am aware of SSL
requiring more message exchanges than should be perceived at the
application level. Allow me to try to be more accurate about what I'm
looking for.
What I would like to do is to use OpenSSL's normal functionality, but
without encapsulation of the actual operation of sending messages.
Instead I would like all messages "forged" by OpenSSL - including
handshake messages - to be sent back up to my module (which would be
implemented in the Oz language I mentionned in my original post). Then
the data would be sent accross the "high level" structured peer-to-peer
network in a reliable way, and the reverse operation run on the other end.
If I understand what Ning Ke suggests, OpenSSL uses a BIO output to send
all those messages regardless of what that BIO is actually encapsulating
? (That would normally be the TCP connexion) If it is so, I believe I
have the answer to my questions.
Thanks again to all those whose time I have stolen
--
Alain Damiral,
Université Catholique de Louvain - student
alain.damiral'at'student.info.ucl.ac.be
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
