<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mesibo End-to-End Encryption - Introduction on mesibo documentation</title><link>https://docs.mesibo.com/api/end-to-end-encryption/</link><description>Recent content in Mesibo End-to-End Encryption - Introduction on mesibo documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.mesibo.com/api/end-to-end-encryption/index.xml" rel="self" type="application/rss+xml"/><item><title>Mesibo End-to-End Encryption APIs</title><link>https://docs.mesibo.com/api/end-to-end-encryption/apis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/api/end-to-end-encryption/apis/</guid><description>&lt;p&gt;There are only two classes to configure mesibo E2EE:&lt;/p&gt;
&lt;h4 id="mesiboendtoendencryption"&gt;MesiboEndToEndEncryption&lt;a class="td-heading-self-link" href="#mesiboendtoendencryption" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;&lt;code&gt;MesiboEndToEndEncryption&lt;/code&gt; is a global class to manage global and per-user E2EE configurations. Mesibo creates an instance of the class which you can access by calling Mesibo.e2ee() function as shown above.&lt;/p&gt;
&lt;h4 id="mesiboendtoendencryption-1"&gt;MesiboEndToEndEncryption&lt;a class="td-heading-self-link" href="#mesiboendtoendencryption-1" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;&lt;code&gt;MesiboProfileEndToEndEncryption&lt;/code&gt; is a class to manage a user-specific E2EE configurations. MesiboProfile creates an instance of the class which you can access by calling MesiboProfile.e2ee() function.&lt;/p&gt;</description></item><item><title>Mesibo End-to-End Encryption - Cryptography APIs</title><link>https://docs.mesibo.com/api/end-to-end-encryption/cipher-suite/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/api/end-to-end-encryption/cipher-suite/</guid><description>&lt;p&gt;mesibo automatically sets optimized cryptography configuration and hence you don’t need to use any of these APIs unless you have special needs.&lt;/p&gt;
&lt;h3 id="setting-supported-and-preferred-ciphers"&gt;Setting Supported and Preferred Ciphers&lt;a class="td-heading-self-link" href="#setting-supported-and-preferred-ciphers" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;mesibo uses 256-bit encryption and supports using multiple ciphers simultaneously to make interception difficult. By default, all the ciphers are enabled. mesibo prefers to use CTR-based and AEAD (authenticated encryption with associated data) ciphers and the AES-GCM is the default preferred cipher. You can change the supported and preferred ciphers by calling &lt;code&gt;setCiphers&lt;/code&gt; method of &lt;code&gt;MesiboEndToEndEncryption&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Mesibo End-to-End Encryption - Man-in-the-middle Protection APIs</title><link>https://docs.mesibo.com/api/end-to-end-encryption/man-in-the-middle/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/api/end-to-end-encryption/man-in-the-middle/</guid><description>&lt;p&gt;It is generally not necessary to configure these options for casual chat. The default end-to-end encryption provides best-in-class security. However, if you are worried about eavesdropping, you can use a secret password, or install the public certificate of the peer. They are included in the per-message encryption process, and these out-of-the-band methods make it nearly impossible for anyone to intercept your communication.&lt;/p&gt;
&lt;h3 id="setting-a-password"&gt;Setting a Password&lt;a class="td-heading-self-link" href="#setting-a-password" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;You can set a password that is included in the encryption process (KDF). The peer needs to use the same password to decrypt the messages. Setting a password can be very effective against a man-in-the-middle attack. Refer to the article link above for the description.&lt;/p&gt;</description></item><item><title>Mesibo End-to-End Encryption APIs</title><link>https://docs.mesibo.com/api/end-to-end-encryption/e2e-progress-3472908472/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/api/end-to-end-encryption/e2e-progress-3472908472/</guid><description>&lt;p&gt;mesibo end-to-end algorithm is an improvement over existing protocol, namely OTR, Silent_Circle_Instant_Messaging_Protocol, and Open Whisper System (used by WhatsApp, Signal, etc).&lt;/p&gt;
&lt;p&gt;improvements&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;third party man in middle elimination&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;improved rachet algoruthm in terms of&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;efficency in key generation&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;imprioved ephernal keys for out of order packets.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;assymetrical key generation where receiver dicates how sender generates key, while maintaining systmmetric cipher&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;indentiy update&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;does not maintain centralize key directory&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;configurable level of strength, same, more, or lower than other algorithm. As an appl developers, you can decide the strength (banking vs dating vs casual chat) depending on bandwidth and cpu usage&lt;/p&gt;</description></item></channel></rss>