Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

127
Vistas
E2EE for DMing / Group DMing (not live chat/socket)

Really curious what the recommendation is to keep user DMs / Group DMs secure for the parties. Been reading on AES-256-GCM and ECDH to build around.

From what I understand,

  1. each user generates their keys (public and private)

  2. when interaction needs to occur, both parties need to compute a shared key using each others public keys.

  3. now Alice, will use the shared key to create a cipher of the message she wants to send to Bob

  4. the cipher itself is saved to the DB

  5. Bob will also use that shared key to decrypt that cipher and read Alice's message.

  6. repeat

There are other parts to this like the authentication (auth tag), but those are pretty self explanatory.

The shared key can remain on each users private domain, but each user will need to retrieve the others public key to create that shared key. Storing the public key of each user on the DB seems unsafe?

Imagine Twitter-esque DMing/Group DMing but E2EE, keeping the messages secure in the DB, authenticated, and immutable.

Some input would be helpful!

about 4 years ago · Juan Pablo Isaza
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda