11
SecureBit.chat - Enhanced Security Edition (securebit.chat)
submitted 5 months ago* (last edited 5 months ago) by to c/privacy@lemmy.ml
8 comments fedilink hide all child comments
 

World's most secure P2P messenger. End-to-end encrypted, zero-server architecture, quantum-resistant roadmap. WebRTC direct connections, advanced ECDH + DTLS + SAS verification, full ASN.1 validation. FOSS

https://github.com/Secureremovedat/securebit-chat

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 5 months ago (2 children)

This is all in js and uses jsx for frontend. Has anyone tried this out yet? Using webRTC is interesting but do t you need a centralized STUN or TURN for ICE policies ?

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 3 points 5 months ago* (last edited 5 months ago)

    I don't think so, all data are on your device and in the one of the other user. No man in the middle. It's similar to the paleolitic finger protocol (which still can be used after more than 50 years), but military grade encrypted.

    Example of the finger protocol write this in your commandline for an message from me:

    finger zerush@happynetbox.com

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 month ago

    Great question.

    WebRTC still relies on STUN and, when direct connectivity isn't possible, TURN for ICE.

    SecureBitChat currently supports ^Direct Mode^, where users exchange the SDP manually (copy/paste, QR code, file, etc.). Once exchanged, the peers establish a direct WebRTC connection.

    Right now, users can configure their own STUN and TURN servers directly in the settings, use public servers, or any infrastructure they trust. An optional assisted connection mode is currently in development.

  • permalink
  • fedilink
  • source
  • parent