Hi,

I work at wolfSSL (creators of the CyaSSL library).  CyaSSL has supported 
both DTLS 1.0 and DTLS 1.2 for quite some time now.  We have had several 
users of CyaSSL running on Android in the past, but have recently taken a 
couple of actions to make doing so easier.

1.  As noted, since Java currently lacks support for DTLS, developers have 
typically had to write their own JNI wrappers around a native SSL library. 
 We thought it would be helpful to have an open source JNI wrapper 
available to save users time and effort in doing so.  We have recently 
created a JNI wrapper around CyaSSL, exposing a Java API to developers. 
 More details, as well as a download link, can be found on the following 
page:  http://yassl.com/yaSSL/Products-wolfssljni.html.

2.  Taking #1 a step further toward Android, we have put together a simple 
reference implementation of how the JNI wrapper, along with CyaSSL, can be 
integrated into a standard Android NDK application.  We haven't published 
this anywhere on the web yet, but feel free to drop us a note at 
i...@wolfssl.com and we'll be happy to email it to you.

Best Regards,
Chris


On Friday, March 16, 2012 4:26:46 AM UTC-6, Echelon wrote:
>
> Hi, 
> I am trying to figure out how can I create a client/server application 
> using DTLS from either OpenSSL or CyaSSL, or even BouncyCastle 
> (SpongyCastle) modifying the sources but I am encountering difficulties in 
> loading the context and specifying the DTLS method in a datagram socket. 
> Anyone has experience or link to guidelines?
>
> Thanks
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Android Security Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-security-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to android-security-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/android-security-discuss.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to