lockbitchat
39aad6ae8b
- add header gear + connection-screen entry points to Advanced network settings - render the ICE settings modal at the app root (reachable from any screen via event) - remove the standalone relay-only toggle/description from the start screen (relay-only now lives in the advanced settings panel) - fix crash from referencing main-component state inside EnhancedConnectionSetup - bump version to 4.8.10 across header, manifest, README, init message, disclaimer - document the feature in CHANGELOG and README
131 lines
4.8 KiB
Markdown
131 lines
4.8 KiB
Markdown
# SecureBit.chat v4.8.10
|
|
|
|
SecureBit.chat is a browser-based peer-to-peer chat application built on WebRTC and Web Crypto APIs. It is designed for direct encrypted communication, explicit peer verification, and a small operational footprint without account registration or server-side message storage.
|
|
|
|
## Security model
|
|
|
|
SecureBit.chat uses:
|
|
|
|
- ECDH key agreement with derived session keys
|
|
- DTLS-protected WebRTC transport
|
|
- deterministic Short Authentication String (SAS) verification
|
|
- end-to-end encrypted chat payloads
|
|
- replay protection and session-state cleanup
|
|
- encrypted local key metadata in IndexedDB
|
|
|
|
A session is not treated as verified until both peers complete the interactive SAS flow. Each user must compare the displayed code with the peer through an out-of-band channel and enter the matching code manually. Three failed SAS attempts terminate the session.
|
|
|
|
## Highlights in v4.8.10
|
|
|
|
- New: users can configure their own STUN/TURN servers under "Advanced network settings" (header gear or the connection-creation screen). Input is allowlist-validated, optionally saved encrypted on-device, and a built-in "Test servers" check reports STUN/TURN reachability.
|
|
- Relay-only privacy mode moved into the advanced settings panel; the standalone start-screen toggle was removed.
|
|
|
|
Earlier in the v4.8 hardening line:
|
|
|
|
- Patched a high-severity XSS advisory in the DOMPurify dependency (the message sanitizer) by upgrading to a fixed release.
|
|
- Operator TURN credentials are no longer committed to the repository; use `config/ice-servers.example.js` as a template.
|
|
- The production logger no longer prints error context or info/debug output, only opaque error codes.
|
|
|
|
- Manual WebRTC setup preserves pending offer/answer state during slow out-of-band exchange.
|
|
- TURN relay fallback can be configured through `config/ice-servers.js` for restrictive networks.
|
|
- ICE diagnostics identify mDNS-only candidate failures without exposing full peer IPs.
|
|
|
|
- SAS verification is bound to the actual DTLS fingerprint strings of both peers
|
|
- chat sanitization uses DOMPurify-backed text-only output
|
|
- WebRTC privacy mode is explicit and relay-only state stays synchronized at runtime
|
|
- production debug window hooks are gated behind an explicit debug flag
|
|
- receiver-side throttling covers inbound messages and file chunks
|
|
- service-worker caching is restricted to an explicit safe-asset allowlist
|
|
- disconnect cleanup leaves no orphaned delayed timer behind
|
|
- `node_modules` is no longer tracked in Git
|
|
|
|
## Quick start
|
|
|
|
### Run locally
|
|
|
|
```bash
|
|
npm install
|
|
npm run build
|
|
npm run serve
|
|
```
|
|
|
|
Then open the local server URL in two browser windows or profiles.
|
|
|
|
### Establish a session
|
|
|
|
1. Create an offer in the first browser.
|
|
2. Transfer the offer to the peer and create an answer.
|
|
3. Return the answer to the first browser.
|
|
4. Compare the SAS code out of band.
|
|
5. Enter the matching SAS code on both sides.
|
|
6. Begin chatting only after both peers are verified.
|
|
|
|
## Configuration
|
|
|
|
### TURN / privacy mode
|
|
|
|
Direct WebRTC connections may expose IP addresses to peers. SecureBit.chat supports a relay-only privacy mode:
|
|
|
|
- default mode keeps normal WebRTC behavior and existing STUN support
|
|
- relay-only mode sets `iceTransportPolicy: "relay"`
|
|
- relay-only mode requires a configured TURN server
|
|
- STUN alone does not hide IP addresses
|
|
- public TURN credentials are not bundled or hardcoded
|
|
|
|
Configure ICE servers at deployment time and enable relay-only mode only when a TURN service is available. See [`doc/CONFIGURATION.md`](doc/CONFIGURATION.md).
|
|
|
|
### File transfer policy
|
|
|
|
Incoming file transfers require explicit user consent. Before the consent prompt appears, metadata is validated and dangerous names are rejected. Safe accepted categories are:
|
|
|
|
- common raster images
|
|
- PDF
|
|
- plain text
|
|
- ZIP archives
|
|
|
|
Executable, scriptable, and high-risk formats are rejected, including `.exe`, `.bat`, `.cmd`, `.sh`, `.js`, `.msi`, `.dmg`, `.app`, `.jar`, `.scr`, `.ps1`, `.vbs`, `.html`, and `.svg`. MIME type and filename extension must agree.
|
|
|
|
## Development
|
|
|
|
### Requirements
|
|
|
|
- Node.js 18+
|
|
- npm
|
|
|
|
### Commands
|
|
|
|
```bash
|
|
npm install
|
|
npm test
|
|
npm audit
|
|
npm run build
|
|
npm run dev
|
|
```
|
|
|
|
### Project layout
|
|
|
|
```text
|
|
src/network/ WebRTC connection and session lifecycle
|
|
src/transfer/ secure file-transfer implementation
|
|
src/crypto/ cryptographic utilities
|
|
src/components React UI components
|
|
doc/ technical documentation
|
|
```
|
|
|
|
## Documentation
|
|
|
|
- [`SECURITY.md`](SECURITY.md)
|
|
- [`doc/CONFIGURATION.md`](doc/CONFIGURATION.md)
|
|
- [`doc/CRYPTOGRAPHY.md`](doc/CRYPTOGRAPHY.md)
|
|
- [`doc/SECURITY-ARCHITECTURE.md`](doc/SECURITY-ARCHITECTURE.md)
|
|
- [`doc/API.md`](doc/API.md)
|
|
- [`CHANGELOG.md`](CHANGELOG.md)
|
|
|
|
## Responsible use
|
|
|
|
SecureBit.chat is intended for lawful, ethical use. See [`RESPONSIBLE_USE.md`](RESPONSIBLE_USE.md) and [`SECURITY_DISCLAIMER.md`](SECURITY_DISCLAIMER.md).
|
|
|
|
## License
|
|
|
|
MIT License. See [`LICENSE`](LICENSE).
|