This project provides a WebRTC-based chat service that enables secure and private communication between a "Host" and a "Peer." The code for this project is provided strictly for use within the offered service. Users are not allowed to use, modify, or redistribute the code outside of the intended service.
- Host Role: The host creates a connection offer and waits for the peer to respond with an answer.
- Peer Role: The peer receives the host's offer, generates a connection answer, and establishes communication.
- Real-Time Chat: Exchange messages securely once the connection is established.
- Peer-to-Peer Data Channels: Direct communication between the host and peer, bypassing intermediaries.
To use the service, follow these steps:
- Open this link.
- Follow the instructions for the Host and Peer setup below.
- Click "Open Host Page".
- Generate a connection offer by clicking "Generate Offer".
- Copy the generated offer and share it with the Peer securely (e.g., through a note, email, or another communication method).
- Click "Open Peer Page".
- Paste the Host's offer into the Offer field.
- Click "Generate Answer" to create a connection answer.
- Share the answer back with the Host using the same secure method.
- Once both sides have exchanged offers and answers, the connection will be established.
- You can start sending messages securely using the chat interface.
This service prioritizes secure and private communication. However, users should take additional steps to ensure maximum security:
-
Key Exchange:
- For the highest security, exchange the Host's offer and Peer's answer through a trusted, offline method like a handwritten note.
-
VPN and Tor:
- For anonymity and IP protection, use a VPN, or combine a VPN with the Tor network for added privacy.
-
Avoid Public Networks:
- Ensure you're using a secure, private network to prevent eavesdropping.
-
WebRTC IP Protection:
- Verify your WebRTC setup does not leak your IP address (use tools to test for WebRTC leaks).
-
One-Time Keys:
- Each session connection should result in the keys being un-usable. If a connection is dropped, both parties will need to re-do the handshake process.
This project is licensed under a custom license:
- Use of the software is permitted only through the provided service.
- Redistribution, modification, or reverse engineering of the code is strictly prohibited.
- For full terms, see the LICENSE file.
This software is provided "as is", without any guarantees or warranties of any kind. The author is not liable for any damages or issues arising from its use.
For questions, feedback, or support, please contact the author.