Re: [Ccrtp-devel] Patches and files for SRTP support

[Werner Dittmann]

David,

during this week I start with the ZRTP integration. As proposed this
would be a new class on top of AVQueue, thus quite independent a nice
add-on to ccRTP. If all goes well then we could have ZRTP in about
2 weeks (need some time to do some interop tests ...).

For error reporting I would propose to do a small enhancement to the
CryptoContext class: provide a method to set a "error-report" callback.
if this callback is not NULL then call a reporting method. Something
along the lines:

class ErrorReport {
        virtual bool authenticationError(const RTPPacket* rtp) = 0;
        virtual bool replayError(const RTPPacket* rtp) = 0;
}

Then some class of the application implement this:

class MyApplication : ErrorReport {

bool authenticationError(...) {
        do something;
        return false;           // dismiss packet
           or
        return true;            // accept packet
}

bool replayError(...) {
        do something;
        return false;           // dismiss packet
           or
        return true;            // accept packet
}

...
CryptoContext ctx = new CryptoContext( ...........);
ctx->setErrorReportCallback(this);

...


If no callback is set in CryptoContext default action could be to do
some error printout (cerr) and to dismiss the erroneous packet.

A similar mechanism will be provided in the ZRTP class. This provides
the ZRTP implementation to report the security states and other information
to the application (e.g. the Short Authentication String, SAS).

Ideas?

Regards,
Werner


David Sugar wrote:
> I would like to do a new release in early August, perhaps during the
> week of the 6th.  I also think this implementation for Secure RTP is
> very workable and should be easy to integrate.  I want to look through
> the changes proposed by Yaniv Levy for better supporting RTSP based
> streaming services as well.
> 
> Federico Montesino Pouzols wrote:
>> Hi Werner, I'll try to integrate your SRTP code a bit later today or
>> tomorrow. I have not looked at your patches yet, but from what I've
>> just skimmed in previous mails your approach seems pretty good.
>>
>> I'll let you know as soon as it is integrated, if there is any issue and
>> if I come up with some idea for error handling. Also, if you plan to work
>> on that issues and have a savannah account, I think David could give you
>> write access to CVS so that your progress is not slowed down.
>>
>>
>>
>>
>> _______________________________________________
>> Ccrtp-devel mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/ccrtp-devel