lockbitchat
cb72b9cb1c
The new composer props (nowTick, codeMode, view-once/timer setters, unsend/expire handlers) were threaded into EnhancedConnectionSetup, but the message list and composer live in the sibling EnhancedChatInterface. After SAS confirmation the verified-state re-render referenced an out-of-scope `nowTick`, throwing "ReferenceError: Can't find variable: nowTick" so the chat never rendered. Move the prop destructuring and pass-through onto EnhancedChatInterface (where the chat UI actually is) and revert the mistaken additions on EnhancedConnectionSetup. No behavioural change to the v4.8.14 features otherwise. Bumps to 4.8.15.
28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
# Security Disclaimer and Terms of Use
|
|
|
|
SecureBit.chat is provided as open-source software for lawful private communication, research, and education. It is supplied **as is**, without warranties of any kind.
|
|
|
|
## User responsibilities
|
|
|
|
By using SecureBit.chat, you are responsible for:
|
|
|
|
- complying with applicable laws and organizational policies
|
|
- securing your devices and browser environment
|
|
- verifying SAS codes through an out-of-band channel
|
|
- understanding that endpoint compromise can defeat application-layer protections
|
|
- configuring TURN correctly when relay-only privacy mode is required
|
|
|
|
## Security limitations
|
|
|
|
No communication system can guarantee absolute security. SecureBit.chat reduces risk through encrypted transport, mandatory peer verification, explicit file-transfer consent, local metadata protection, and lifecycle cleanup, but it cannot protect against compromised devices, malicious users with physical access, or incorrect operational practices.
|
|
|
|
## Intended use
|
|
|
|
SecureBit.chat is intended for legitimate private communication, journalism, research, education, business confidentiality, and personal privacy. It is not intended to facilitate unlawful activity, abuse, harassment, or harm.
|
|
|
|
## Current release
|
|
|
|
- Product release: `v4.8.15`
|
|
- Protocol version: `4.1`
|
|
- Last updated: May 17, 2026
|