Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

131
Views
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
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!