encryption

[Петр (Simon's Cat)]

Please tell me how messages are protected? And traffic between client and server. Is ssl pinning available? And does the server know about the contents of the messages?

[Gene]

On Saturday, June 22, 2024 at 10:05:53 AM UTC-7 Петр (Simon's Cat) wrote:

Please tell me how messages are protected?

TLS

 

And traffic between client and server.

TLS

 

Is ssl pinning available?

No.

 

And does the server know about the contents of the messages?

Yes.

 

[Петр (Simon's Cat)]

And where exactly is TLS encryption enabled? Where can I watch it? In what function?

воскресенье, 23 июня 2024 г. в 03:24:11 UTC+9, Gene:

[Gene]

On Saturday, June 22, 2024 at 9:22:09 PM UTC-7 Петр (Simon's Cat) wrote:

And where exactly is TLS encryption enabled? Where can I watch it? In what function?

https://github.com/tinode/chat/blob/a97c49477fae478062238049e6cde2da2fe9c114/server/http.go#L79

[Петр (Simon's Cat)]

Thank you very much for the answer.
How soon will the end-to-end encryption feature be available?
And if I want to do general encryption, say, with an NPP key, where is the best place to implement this?

понедельник, 24 июня 2024 г. в 00:50:57 UTC+9, Gene:

[Gene]

On Monday, June 24, 2024 at 5:12:30 AM UTC-7 Петр (Simon's Cat) wrote:

Thank you very much for the answer.
How soon will the end-to-end encryption feature be available?

When someone pays for it or contributes it.

https://github.com/tinode/chat/issues/357

And if I want to do general encryption, say, with an NPP key, where is the best place to implement this?

I don't know what you mean by general encryption and NPP key. 

[Петр (Simon's Cat)]

So that all messages, files, and other things are encrypted with the AEC algorithm

вторник, 25 июня 2024 г. в 00:07:44 UTC+9, Gene:

[Gene]

On Monday, June 24, 2024 at 8:09:49 AM UTC-7 Петр (Simon's Cat) wrote:

So that all messages, files, and other things are encrypted with the AEC algorithm

I understand what "encryption" means. I don't understand what you mean by "general encryption, say, with an NPP key".

[Петр (Simon's Cat)]

The simplest option. The client's all text messages are encrypted with AES. Those. Client writes “hello” from her phone, this is encrypted with any key. Let's say "123" and as a result we will get the string "U2FsdGVkX1+5LZamGRD8TjfDLohaX+fFsD5xK1QfhWU=". For another client it is decrypted and that’s it. Those. This way we protect that the data will be read if the TLS protocol is not used.

вторник, 25 июня 2024 г. в 00:19:38 UTC+9, Gene:

[Gene]

On Monday, June 24, 2024 at 8:30:44 AM UTC-7 Петр (Simon's Cat) wrote:

The simplest option. The client's all text messages are encrypted with AES. Those. Client writes “hello” from her phone, this is encrypted with any key. Let's say "123" and as a result we will get the string "U2FsdGVkX1+5LZamGRD8TjfDLohaX+fFsD5xK1QfhWU=". For another client it is decrypted and that’s it. Those. This way we protect that the data will be read if the TLS protocol is not used.

I would suggest you to start learning about encryption, key exchange algos such as double ratchet and Diffie-Hellman, etc. You can start with this wikipedia article: https://en.wikipedia.org/wiki/Double_Ratchet_Algorithm

Once you have a coherent idea of what you want to do, put it in writing, like an RFC then share it here.