Werner Dittmann

Am 22.10.2015 um 14:48 schrieb Werner Dittmann: > May take a few days, I need to update my Go enviroment first. Actually I'm > suprised that GoRTP is used at...

IMHO you need a bi-directional data path between the ZRTP glue code and the SIP/RTP part, similar to this: +----------+ | RTP | | SRTP | +----------+ | . |...

Am 06.11.2015 um 11:45 schrieb NicholasDong: > Hi Werner, > > Thanks for your quick answer. But I have some questions: 1. Do you > mean that the RTP/SRTP stack...

Actually, I don't think so. ZRTP protects every packet with an HMAC, and this is true the the Hello and commit packets as well. Thus if a MitM modifies the...

You are not alone - it's somewhat complex and I discussed with Phil several hours to get all this :-) . Some points: - you are right with the Hash...

I had some discussion with Phil about this topic and we came up with the following handling: If the ZID in the commit does not match the ZID from the...

Am 05.07.2013 20:39, schrieb matthewdgreen: > I admit to being a bit flummoxed by the code for this. As best I can tell the current ZRTPCPP code receives a Hello,...

Am 06.07.2013 09:56, schrieb matthewdgreen: > Ok, I had to read Travis's note several times before I realized he was discussing a future version in which both Hello messages are...

I cannot confirm this. In the shown function the sequence is: ... if (algorithm == SrtpEncryptionAESCM || algorithm == SrtpEncryptionAESF8) { AESencrypt *saAes = new AESencrypt(); if (keyLength == 16)...

This is similar to your first report. The destructor takes care of deallocation. Similar to the bigbytes code as I can see this. It's the bnEnd function that takes carte...