[sip-comm-dev] Switching to BouncyCastle Lightweight crypto API


#1

Dear all,

as discussed in some posts we need to get rid of the Java JCE
crypto provider because this complicates matters when distributing
and installing SC with ZRTP and SRTP.

Currently I'm working on this. In my sandbox I already modified
the SRTP code to use the BC lightweight (LW) API only. During these
modifications I also did some code optimizations that reduce the number
of "new" operations per SRTP packet: we save 7 "new" operations
per SRTP packet.

The ZRTP engine is next.

Because the modifications affect a larger part of SRTP and ZRTP code
I would ask not to do too much modifications in the
*.impl.media.transform packages - this could result in much conflicts.

I'll check in these modifications after FOSDEM :slight_smile: .

Regards,
Werner

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Werner,

Werner Dittmann wrote:

Dear all,

as discussed in some posts we need to get rid of the Java JCE
crypto provider because this complicates matters when distributing
and installing SC with ZRTP and SRTP.

Currently I'm working on this. In my sandbox I already modified
the SRTP code to use the BC lightweight (LW) API only. During these
modifications I also did some code optimizations that reduce the number
of "new" operations per SRTP packet: we save 7 "new" operations
per SRTP packet.

Wow, that was quick:) Thanks for being so reactive!

The ZRTP engine is next.

Because the modifications affect a larger part of SRTP and ZRTP code
I would ask not to do too much modifications in the
*.impl.media.transform packages - this could result in much conflicts.

I've already made some modifications on the patch I've sent you, taking
in to account your comments. I'll send you a patch until this evening, would you be able to check it out?

Regards,
Yana

···

I'll check in these modifications after FOSDEM :slight_smile: .

Regards,
Werner

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Yana,

I can try to have a look - howvere, the modifications in your
patch w.r.t. ZrtpTransform stuff are not critical. This class
has only some small updates at all.

Regards,
Werner

Yana Stamcheva schrieb:

···

Hi Werner,

Werner Dittmann wrote:

Dear all,

as discussed in some posts we need to get rid of the Java JCE
crypto provider because this complicates matters when distributing
and installing SC with ZRTP and SRTP.

Currently I'm working on this. In my sandbox I already modified
the SRTP code to use the BC lightweight (LW) API only. During these
modifications I also did some code optimizations that reduce the number
of "new" operations per SRTP packet: we save 7 "new" operations
per SRTP packet.

Wow, that was quick:) Thanks for being so reactive!

The ZRTP engine is next.

Because the modifications affect a larger part of SRTP and ZRTP code
I would ask not to do too much modifications in the
*.impl.media.transform packages - this could result in much conflicts.

I've already made some modifications on the patch I've sent you, taking
in to account your comments. I'll send you a patch until this evening,
would you be able to check it out?

Regards,
Yana

I'll check in these modifications after FOSDEM :slight_smile: .

Regards,
Werner

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net