Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Brand
brandclient
Professional uses an encryption and security system based on ZRTP protocol. This protocol is based on human verification of two words (called Short Authentication String or SAS) displayed at the beginning of a call. The SAS are made up of two words in English, randomly generated for each call. The same SAS displayed on the two phones must be verbally compared by the two callers to guarantee call security. After the security was verified the two peers could trust each other.

Verify call security

...

matching

...

keys means the call is secure!

...

on the phone
Subtitle
Prefixfigure
SubtitleTextSAS on the callercaller' SAS must match callee's phoneone
AnchorNamebb_sas 1_untrusted
Image Modified
Subtitle
Prefixfigure
SubtitleTextcaller' SAS
must match callee's
one
AnchorName
bb sas 2
Image Removed

 

iphone sas 1
Subtitle
Prefixfigure
SubtitleTextThe caller reads his key out loud
AnchorName

The caller reads his key out loud (

Xref
AnchorNamebb sas 1
) and the callee can check they match his owns (
Xref
AnchorNamebb sas 2
).

Verify call security on iPhone:  matching key exchanges, so the call is secure!

iphone_sas_untrusted
Image Modified
Subtitle
Prefixfigure
SubtitleText
The called party makes sure it matches his one
AnchorNameiphone sas 2
Image Removed

 

 

The caller reads his key out loud (

Xref
AnchorNameiphone sas 1
) and the callee can check they match his owns (
Xref
AnchorNameiphone sas 2
).

Verify call security on Android:  matching key exchanges, so the call is secure!

The called party makes sure it matches his 2
Subtitle
Prefixfigure
SubtitleTextThe caller reads his key out loud
AnchorNameandroid sas 1

Image Removed

Subtitle
Prefixfigure
SubtitleText
caller' SAS must match callee's one
AnchorNameandroid_sas
_untrusted
Image Modified

 

The caller Caller reads his key out loud (

Xref
AnchorNameandroid sas 1
) and the callee can check loud and callee checks they match his owns (
Xref
AnchorNameandroid sas 2
).

 

Note
titleSuggestion
After making sure the Short Authentication Strings match and that the called party is really the person you are speaking to, save the contact in the phone book as "trusted" by clicking Trust. This way you need not verify the key exchange next time you call this (trusted) contact in the future.The Short Authentication Strings will no longer be highlighted in orange. Security is guaranteed by the ZRTP key continuity feature.

In normal conditions subsequent communications with a "trusted" contact can start without the need of verbal verification. Short Authentication Strings background color will be different and SAS should only be verified in the event of wiretapping attempts or change to one of the two phones' configurations. In this case, the keys must be verbally verified or the call immediately interrupted.

Secure call between trusted contacts

Subtitle
Prefixfigure
SubtitleTextTrusted contacts
AnchorNamebb_trusted_contacts
Image Added
Subtitle
Prefixfigure
SubtitleTextTrusted contacts
AnchorNameiphone_trusted_contacts
Image Modified
 

 

...

Subtitle
Prefixfigure
SubtitleTextTrusted contacts
AnchorNameandroid_trusted_contacts
Image Added
Warning
titleWarning

If the SAS does not match with your peer's one you should immediately hang up the call as this might be a sign of a Man in the Middle interception attack.

...

In the event of a third party attempts to wiretap a call when you're speaking to a contact not yet saved as trusted,

Brand
brandclient
displays two displays different Short Authentication String on the two phones. The callers caller should verbally verify the differences between the two key exchanges and interrupt the call.

NON matching key exchanges: wiretapping attempt in progress!

Subtitle
Prefixfigure
SubtitleTextSAS on the caller's phone
AnchorNamewiretap 1
Image Removed
Subtitle
Prefixfigure
SubtitleTextSAS on the calle's phone don't match
AnchorNamewiretap2
Image Removed

 

 

 

Navbar