|Subject:||Re: [Linphone-developers] b256 SAS implementation for bzrtp|
|Date:||Tue, 10 Mar 2015 17:19:59 +0000|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0|
The problem with your SAS solution is not everyone talk English,|
and the second problem with English is that the words are not always pronounced as it is written (that's the first problem I faced in the days I began to learn English) thus
it would add another ambiguity when pronouncing words by someone who had never knew about English.
Your proposition is inspired from the navy and military, however this is about trained people not for everyone as it is intended in Linphone !
على 10 مار, 2015 ص 10:48, كتب Eli Burke:
Building on Ben Sartor’s excellent BZRTP patches to add support for the non-mandatory algorithms, here are patches to add the b256 SAS format. Instead of returning a 4 character SAS string like “7jb3” it will return two words such as “seabird:asteroid”. Per the RFC, the words come from the PGP Word List and should not be localized: http://en.wikipedia.org/w/index.php?title=PGP_word_list oRTP and ms2 need small patches to extend the length of the SAS variable in the eventData structure. liblinphone was patched to add linphonerc overrides for each set of algorithms. No default values are changed from stock Linphone: Ben’s patch sets sensible ZRTP defaults based on the config setting for “srtp_crypto_suites”, this patch adds e.g: zrtp_key_agreements_suites=MS_ZRTP_KEY_AGREEMENT_EC38 zrtp_cipher_suites=MS_ZRTP_CIPHER_AES3 zrtp_auth_suites=MS_ZRTP_AUTHTAG_HS80 zrtp_hash_suites=MS_ZRTP_HASH_S256 zrtp_sas_suites=MS_ZRTP_SAS_B256 Note that due to the nature of the ZRTP spec, the mandatory algorithms are always added and used during the initial ZRTP handshake, so it is not necessary to specify B32 to be backwards compatible with older clients.
|[Prev in Thread]||Current Thread||[Next in Thread]|