[erlang-questions] DTLS/SRTP for WebRTC

[pablo platt]

Thank you Ingela for your update.

Does anybody have an interest in DTLS for WebRTC and can help improve this
library until OTP will have official support?
It is almost done.

On Sun, Nov 2, 2014 at 9:03 PM, Ingela Andin <ingela.andin@REDACTED> wrote:

> Hi!
>
> 2014-10-30 22:33 GMT+01:00 pablo platt <pablo.platt@REDACTED>:
>
>> Hi,
>>
>> What is the state of DTLS in OTP?
>>
>
> Alas Ericsson has prioritised quite a few other things higher than DTLS
> just lately so the implementation has been delayed.
> I hope it will get back on track soon but I am afraid you can no count on
> it in a short term perspective.
>
> Regards Ingela Erlang/OTP team - Ericsson AB
>
>
>
>>
>> I'm interested in using DTLS/SRTP in Erlang for WebRTC.
>>
>> I've found two implementations:
>>
>> Clean code but I couldn't make it work because it's missing SRTP support.
>> https://github.com/RoadRunnr/otp/tree/new_crypto_dtls
>>
>> This works quite well. I'm able to connect clients to the server:
>> https://groups.google.com/d/msg/discuss-webrtc/MP-1sCrOljA/qAs4VK-18y4J
>>
>> The problem is that some clients can't connect and I'm getting HANDSHAKE
>> packets while in the CIPHER state in the following order:
>> HANDSHAKE, SERVER_HELLO
>> HANDSHAKE, CERTIFICATE
>> HANDSHAKE, SERVER_KEY_EXCHANGE
>> HANDSHAKE, CERTIFICATE_REQUEST
>> HANDSHAKE, SERVER_HELLO_DONE
>>
>> I'm assuming that is related to wrong state change or retransmission.
>> The code only implement retransmission for two packet types and have the
>> following comment:
>> %% problem remainning: different strategy should be adopted while
>> state==hello or cipher.
>>
>> Does anyone use DTLS/SRTP in Erlang and help solve this issue or
>> recommend another solution?
>>
>> Thanks
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141104/ae442a68/attachment.htm>