how to Improve security in minisip?
Cesc
cesc.santa at gmail.com
Tue May 15 13:51:26 CEST 2007
On the ietf rtpsec group, there is quite some chatter about
multiplexing DTLS and RTP on the same transport addresses in order to
negotiate keying for SRTP ... they are pushing this instead of ZRTP,
which violetes layer separation ...
Anyway, take a good look at IETF's rtpsec work group's work ... it is
interesting.
Cesc
On 5/14/07, Mikael Magnusson <mikma264 at gmail.com> wrote:
> Nuno Carvalho wrote:
> > Hi,
> >
> >
> >
> > I´m interested in developing new security features in minisip for my master
> > thesis but I need some ideas of what to do or what to find.
> >
> > I already install a openser and use a secure connection with minisip.
> >
> > Please a need some help to start.
> >
> >
> >
> > Best regards,
> >
> > Nuno Carvalho
> >
>
> 1) sdescriptions RFC 4568. Doesn't really improve security, but
> interoperability. Sdescriptions is similar to MIKEY NULL, and needs
> S/MIME for end-to-end security. But most implementations only supports
> TLS, ie. hop-by-hop security and possibility for proxies to eavesdrop on
> the conversations.
>
> 2) Extend ZRTP support to latest draft. It's probably a matter of
> updating to current ZRTP implementation from GNU ccRTP.
>
> ZRTP is under evaluation by RTPSEC working group:
>
> http://www.ietf.org/internet-drafts/draft-wing-rtpsec-keying-eval-02.txt
> http://www3.ietf.org/proceedings/07mar/minutes/rtpsec.txt
>
>
> Mikael
> _______________________________________________
> Minisip-devel mailing list
> Minisip-devel at minisip.org
> http://lists.minisip.org/mailman/listinfo/minisip-devel
>
More information about the Minisip-devel
mailing list