[sip-comm-dev] ZRTP integration update


#1

Hello Romain, Werner,

Good news. I've managed to carry on the first SC-SC call secured through ZRTP4J (actually I didn't check it deeper than the notifications displayed, but all seems fine according to the SAS, and the other ZRTP4J provided messages). I also added some provisional GUI support for displaying the SAS, and removed some more bugs.

For a detailed description of all these, please check my last dev blog entry ( http://sipcommkeysharing.blogspot.com/ ). I've updated also the sources on the SC svn encryption branch (to Werner: let me know if it's more convenient for you to keep posting an archive with the modifications on my blog).

Regards,
Emanuel

···

--
--------------------------------------------------------------------

"Life is full of unexpected but nothing happens without a reason..."

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


#2

Emanuel,

sorry for the problems with unrestricted policy - I should have
pointed that out. There is also a small programm in the demo folder
that tests all required security algorithms and reports problems.

As you said in your Blog: disabling security during the call is not
possible - goClear is not implemented and once a secure call was
established you cannot simply switch to unsecure - only GoClear
can do that.

What one can do: if one side starts "security enabled" and the other
side "security disabled" and after some time this side switches to
"security Enabled" then ZRTP would automatically setup a secure call
(need to call "enableZrtp()" when the user prsses the "security enabled"
button. However, these are now usage issues - once the first call was
successful the rest will come :slight_smile:

Regards,
Werner

Onica S. Emanuel schrieb:

···

Hello Romain, Werner,

Good news. I've managed to carry on the first SC-SC call secured through ZRTP4J (actually I didn't check it deeper than the notifications displayed, but all seems fine according to the SAS, and the other ZRTP4J provided messages). I also added some provisional GUI support for displaying the SAS, and removed some more bugs.

For a detailed description of all these, please check my last dev blog entry ( http://sipcommkeysharing.blogspot.com/ ). I've updated also the sources on the SC svn encryption branch (to Werner: let me know if it's more convenient for you to keep posting an archive with the modifications on my blog).

Regards,
Emanuel

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


#3

Hi Emanuel,

···

On 2008/06/23, at 16:20, Onica S. Emanuel wrote:

Good news. I've managed to carry on the first SC-SC call secured through ZRTP4J

This is an excellent work, congratulations!
I just came back from traveling and this is a great news to start the week :slight_smile:

Cheers,
romain

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


#4

Thank you for the feedback and the indications! I'll try during this week, as I've written on the blog, to solve the part with switching during a call from "security disabled" to "security enabled". About your question in the previous mail, yes I managed to get some "real time" audio :slight_smile: through, having a conversation with myself, between my desktop PC and the nearby notebook I'm using for testing. Anyway, the ZRTP exchange failed in the DH1/DH2 phase in two or three runs but all went fine after and I didn't manage to find out what was causing it. I've done some (probably unrelated) modifications since that happened but I should do more tests to see if all is fine.

Regards,
Emanuel

···

On Mon, 23 Jun 2008, Werner Dittmann wrote:

Emanuel,

sorry for the problems with unrestricted policy - I should have
pointed that out. There is also a small programm in the demo folder
that tests all required security algorithms and reports problems.

As you said in your Blog: disabling security during the call is not
possible - goClear is not implemented and once a secure call was
established you cannot simply switch to unsecure - only GoClear
can do that.

What one can do: if one side starts "security enabled" and the other
side "security disabled" and after some time this side switches to
"security Enabled" then ZRTP would automatically setup a secure call
(need to call "enableZrtp()" when the user prsses the "security enabled"
button. However, these are now usage issues - once the first call was
successful the rest will come :slight_smile:

Regards,
Werner

Onica S. Emanuel schrieb:

Hello Romain, Werner,

Good news. I've managed to carry on the first SC-SC call secured through ZRTP4J (actually I didn't check it deeper than the notifications displayed, but all seems fine according to the SAS, and the other ZRTP4J provided messages). I also added some provisional GUI support for displaying the SAS, and removed some more bugs.

For a detailed description of all these, please check my last dev blog entry ( http://sipcommkeysharing.blogspot.com/ ). I've updated also the sources on the SC svn encryption branch (to Werner: let me know if it's more convenient for you to keep posting an archive with the modifications on my blog).

Regards,
Emanuel

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

--
--------------------------------------------------------------------

"Life is full of unexpected but nothing happens without a reason..."

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