Hi,

there is some sort of confusion here, lime as intended in Linphone has nothing to do with the lime described on

http://limeprotocol.ORG/

It's just a name collision...

In the linphone referential LIME stands for Linphone Instant Messaging 
Encryption and as described on
https://linphone.org/dokuwiki/doku.php/liblinphone:lime

is a way to perform end to end encryption for messages between two linphones 
clients.

Hope this clarifies.

Regards,

johan

On 20/11/16 08:26, J G Miller wrote:
At 19:27h, on Friday, November 18, 2016,
in message <cahzfiz6ycprtz7w0pn0aoy9zuzv-a5+wcn8q3yj+3f4wysa...@mail.gmail.com>,
on the subject of "[Linphone-users] lime encryption",
Russel Treleaven

  > What is lime encryption?

Is it definitely "encryption with lime [as in cipher]" that you are looking
for as it would appear that you may be looking for lime protocol with 
encryption?

All you want to know about the Lime protocol and more is at

             <http://limeprotocol.ORG/>

including

QUOTE


     LIME Protocol (acronym for Lightweight Messaging Protocol) is a
     JSON based protocol for messaging, inspired by the XMPP protocol

...

  encryptionOptions - Encryption options provided by the server during the
  session negotiation. Some of the valid values (not limited to) are:

     none - The session will be not encrypted.

     tls - The session will be encrypted by TLS. This options is required for
  transport authentication in TCP transport connections.

  encryption - The encryption option selected for the session. This property is
  provided by the client in the negotiation and by the server in the 
confirmation
  after that.

UNQUOTE

Apologies if I am misinterpreting what you are trying to find.

_______________________________________________
Linphone-users mailing list
Linphone-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-users

_______________________________________________
Linphone-users mailing list
Linphone-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-users

Reply via email to