The most secure P2P messenger with military-grade cryptography

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/Secure*removed*at/securebit-chat

  • armrecords@lemmy.ca
    1·
    2 days ago

    Thank you all for your interest in SecureBitChat and for taking the time to check out the project! We recently completed a full redesign of the application and are actively working on the next major update. Some of the features currently in development include:

    • Audio and video calling
    • Mesh groups with multiple simultaneous peer-to-peer connections
    • Faster connection establishment
    • The ability to create and manage entities for quickly reconnecting with trusted contacts and sessions

    Your feedback and questions are incredibly valuable and help shape the direction of the project.

    Thanks again for the support, and stay tuned-there’s much more to come!

  • IratePirate@feddit.org
    6·
    4 months ago

    Hilarious bad-word filtering of the link right there! For anyone wondering: the link will only work if you replace the “removed” part with the word describing a female dog.

    • Zerush@lemmy.mlOP
      7·
      4 months ago

      Yes, certainly a bad joke by this oversensible Lemmy US Flanders filter 🤬Forbidden Use of Carnal Knowledge it (to avoid censoring)

      • Lytia @lemmy.todayEnglish
        2·
        4 months ago

        Is the censoring of words like bitch instance specific? If so, incredibly ironic for lemmy.ml of all places to be censored.

  • Ulrich@feddit.orgEnglish
    1·
    4 months ago

    SB1:bin:eJyVVQuMFWcZ3QUKuGEptKU9gpIpsWpL7u68Z-6vV9m9dylUwLUsXcRqOnfmv3eHva_OzL4QRbQ-CqUFIrKkGB4uMbRQarCND7C2alJKa3kY24rQoKVNWhL6ErRNq-euxVSJiWaz98788_3fOd8555-710tktVCQkRcPjXmiP6M2N1UzKcW0bFNzXd2wHN1yVd3QLEVX5i9S5neaiqY7LSr_tOamOJNqbkoyqsJ9XqYYVftqon3JotyCjn-uyMGk7NVSXqlUHUiVw0EZ1FfLcRikYln2KknoC6V74eLmpnLGq9VKoe8lYbWimHo67ShLcp2tua4Fi1sXZ7s6lQGZjxI_FXiJ5_d4lYosNTf5mYucTLvFIaW01eKm6xi-VwlC1kphWLpm6Kbq2oqm9AU1RbMdx9HTlmH9-7b3UJOhmhJHhdKgEnlBECnq6LCqEtWqUaKoSlFWKNcoTVWpyGSgGvWm_GqcKOn0f0Cbmqa7rqaq5vuhDV1NU05PDYRlq6pwhWsIoTmKbbiOewm-EP87dOjLVF8h8opieRB1XFypDQRiwdLybGPJUHetV79J7_ucUTWMfOGWLv1iTbVWbxuLJAr93pKsLxfCSlFGtSisJCLu8VK6ZSsdlmibK8ycUNPCbKe2wjWFbgtTFaYt2g1h6MJMi3ZTOKawWabWn6o5kesQuTbRbokOW6QdYVsiq4q2rGjrEBpbuUKzRS5Xh41lwhR5flLz4ng0LmEgRtMUcy1Vl0JYqjq6UvYGU2UZx15RpuJwhSSYrpkmH_X7ZouaT-IZDQ2NW7_WNWJ4clexVw51DdVk0JHNzavf5Jil4UGo6Ic6ZfwE3IBvYR5-i8yYxvGXYTZWj2vArLHIN4zDH_Ep_BSfxxr0YiM-iZn4O76HW_E3_Ai_5p2Lr-Im_h-AzgbteBl_weuYjk14Gz6WsKqHK8vRx6sOPDaVDz-EPViL1ml4lDXPc–ZSXikAfuvwjO4uZG9j-IcjiCPHI41NmMEnbgRq7GOPH7Bz6PI4k7S_TrexLO4DyNTG_AiZ9k7rQkz8GVsC5OQ2iReufaeCCt3F_tlFNPnujhhHBYrXtIXyeHb8EFifp8Nb8eDBHwId2A-Sd1FfifwS5g4T-ALuB_3IsRtBHkK-3A3vog_YAN3PI_seHyMI1l4EquwGz9ADftxEmm8hq1ssJtzfxMKv02cacDayYT6CZ7j6g6cgkb9j5DxCXTzKoM5aONkAgE-StV3YcMkNv0NMhNhE_Tb2NeILjZTsQynveBftkraurjt__T1O3SuhSzP4hVWf5x-ziHyVha9Q6fWYOaVeLyJQNdxiluJ_TKrXXwJFWzh8xW8P4CTE3hxnHptYUwOooBZHOsMXsVfqd9z3HQB63EPhzuH7WilTIcm4Wn88Bq2v7NxMjaThEN9r2dEPO6YhZ1YQGmO496x-DHL32ZUluErVPDD-DOdP4Q3L_X2_v_q7UY8eBnTgZ9z-yM0ZTo5zSSXCC8Q-3ZaMsyhVtKIk_gdDk68gjG1yfNXmD3mcizkvvN4jJzcqTiMYxRyMz5CQzrpm9GM1VdQj0MwcAubPIvDVzMlT_MQnMK7RFs1GW9gLvZyjjroSp6EHfTlE-yzAp9mgB5n-2vH8EiYZNTKlstx37h8XBqew7sBcngHVap2iJAh26zGNmZvGWXvxksMzSKUyW0u79cToptpPE2mnfj9qB_rce4D9PIsDl_O_vtx4moWlaeMdtjMbhtGnVnKo7WbOO_S9GUsfhSr8nE4qDjSUX1Vk_wlLOhBITDyhuPZumGaTkEWDC3vhzXNMA0_KNh64FiS7_l8v9-jZ1OannLsvOePhPypKpUkX6TDKn5G6Q_gAUKv4NF6i6HMYvt4TpcnD4NR387jY-G6Rjr9DHXpY-Y2UfMe0lrFZP6JsZg5ludtB3NiIkXfsnz5vEVlrr0kECO6rDAMcj0N2ANJhM_iG3iYR7PIlH4B3-XnOnwGbe_PjR-X-v2FbUvzvYWdniw5Ba9gu4FteHraC0q-YZvpvOsUfBn8A3X4gOE

  • nixFREAK@sopuli.xyz
    1·
    4 months ago

    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 ?

    • armrecords@lemmy.ca
      1·
      2 days 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.

    • Zerush@lemmy.mlOP
      3·
      4 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