21 Commits

Author SHA1 Message Date
lockbitchat
241212a315 🔧 Improve file transfer system integration and message handling
- File Transfer Integration: Refactored file transfer system initialization with better error handling and automatic retry mechanisms
- Message Filtering: Added comprehensive message filtering system to prevent file transfer and system messages from appearing in chat UI
- Callback System: Simplified file transfer callback system - removed progress notifications from chat to reduce noise
- System Message Deduplication: Implemented notification flags to prevent duplicate system messages (verification, security upgrades, etc.)
- Error Handling: Enhanced error handling with graceful fallbacks instead of throwing exceptions that could break connections
- UI Message Delivery: Added `deliverMessageToUI()` method with built-in filtering for system/file messages
- DataChannel Event Handling: Improved onmessage handler with early filtering for file transfer messages
- Global Integration: Better integration with global file transfer system (`window.fileTransferSystem`)
- Connection Stability: Removed aggressive reconnection attempts that could cause session closure
- Debug Logging: Enhanced debug logging for better troubleshooting

- File transfer messages now bypass chat UI entirely
- System messages are deduplicated using internal flags
- Better separation of concerns between WebRTC and file transfer systems
- More robust initialization sequence with proper cleanup
- Improved message routing and processing pipeline

- Fixed duplicate system notifications
- Resolved file transfer message leakage into chat
- Improved connection state management
- Better handling of initialization race conditions
2025-08-20 18:19:42 -04:00
lockbitchat
773215264f Improved chat UX/UI:
- Fixed message auto-scroll bug when receiving new messages
- Adjusted bottom chat section integration with proper styles
- Updated bottom chat section layout and appearance
- Hidden scrollbars for better interaction and cleaner look
2025-08-20 03:53:58 -04:00
lockbitchat
ebcddca40d Merge branch 'main' of https://github.com/lockbitchat/lockbit-chat 2025-08-19 21:56:10 -04:00
lockbitchat
94ca53f6ca Improve chat UI for secure channel creation pages
Fix iOS PWA installation and improve cross-platform compatibility

- Fix manifest.json paths (use relative paths with ./ for iOS)
- Update Apple Touch Icons structure to use organized folders
- Add missing 180x180px icon requirement for iOS
- Fix apple-mobile-web-app meta tags configuration
- Add viewport-fit=cover for iPhone X+ notch support

- Fix missing showInstallButton() method causing TypeError
- Add complete showInstallBanner() and createInstallBanner() methods
- Implement proper hideInstallPrompts() functionality
- Add iOS-specific installation instructions modal
- Fix event handling for install prompt dismissal

- Restructure PWA icons into platform-specific folders:
  - ./logo/pwa/ios/ for Apple Touch Icons
  - ./logo/pwa/android/ for Android launcher icons
  - ./logo/pwa/windows11/ for Microsoft Tiles
- Update manifest.json to reference correct icon paths
- Add browserconfig.xml for Windows 11 tile configuration

- Improve PWA registration script without conflicts
- Add proper error handling for offline functionality
- Integrate with existing PWA modules (install prompt, offline manager)
- Add update notifications for new app versions

- Enhanced detection for iOS Safari vs other browsers
- Improved installation flow for different platforms
- Better user feedback for unsupported installation methods
- Added fallback instructions for manual installation

- Add comprehensive PWA support detection
- Implement proper iOS standalone mode detection
- Add console logging for installation status tracking
- Include developer utilities for PWA management

Tested on: iOS Safari, Chrome, Edge, Firefox
Resolves iOS PWA installation issues and improves overall PWA experience."
2025-08-19 21:54:17 -04:00
SecureBitChat
ac0e5155d3 Update README.md 2025-08-19 19:59:03 -04:00
lockbitchat
91ea88503e Merge branch 'main' of https://github.com/lockbitchat/lockbit-chat 2025-08-19 11:57:34 -04:00
lockbitchat
22b89e0a9d new API keys for test 2025-08-19 11:57:08 -04:00
SecureBitChat
c58896ef55 Update README.md 2025-08-19 02:06:27 -04:00
lockbitchat
fe611f7630 Refactored file encryption/decryption logic for P2P transfers
- Reworked the core logic for encrypting and decrypting files exchanged between users
- Improved key derivation and session handling for file chunks
- Enhanced integrity checks to prevent tampering and replay attacks
- Work in progress: adding hardened encryption schemes and conducting fault-tolerance testing
2025-08-18 23:56:10 -04:00
lockbitchat
dadc80a755 wip(encryption): experimental support for encrypted file transfer via chunks
Added an early implementation of secure file transfer using chunk-based encryption.
Files are split into encrypted chunks and transmitted over the chat channel.

This feature is still under active development and requires further changes and testing.
2025-08-18 21:45:50 -04:00
lockbitchat
857d7d74ab Encryption module control system & session timer improvements
- Added a real verification system for active encryption modules, giving users full control over enabled modules.
- During session purchase or activation, the actual enabled modules are now displayed for both free and paid sessions.
- Refactored session timer initialization for proper functionality and accurate countdown.
- Optimized code structure related to session management and module verification.
2025-08-17 20:38:47 -04:00
lockbitchat
8d35a309a5 update for correct file loading 2025-08-17 16:51:41 -04:00
lockbitchat
8b134fd410 update for correct file loading 2025-08-17 16:49:04 -04:00
lockbitchat
7583cdc5e8 update for correct file loading 2025-08-17 16:45:30 -04:00
lockbitchat
f1e57fe0f1 - SECURITY_DISCLAIMER.md: Developer liability protection
- RESPONSIBLE_USE.md: Ethical usage guidelines
- Supports digital rights while ensuring responsible use
2025-08-17 16:31:22 -04:00
lockbitchat
3c25b4565d feat: Add comprehensive PWA support with offline functionality
- Add manifest.json with full PWA configuration
  - Support for installation on all platforms (iOS, Android, Desktop)
  - Custom app icons (72x72 to 512x512) with maskable support
  - App shortcuts for quick actions (Create/Join Channel)
  - Protocol handlers for web+securebit:// links
  - Share target integration

- Implement enhanced Service Worker (v4.0)
  - Smart caching strategies (cache-first, network-first, stale-while-revalidate)
  - Security-aware caching (excludes sensitive endpoints)
  - Background sync for failed requests
  - Offline fallbacks with custom error handling
  - Response cloning fixes and CORS handling

- Add PWA Install Prompt Manager
  - Cross-platform install detection and prompts
  - iOS Safari specific installation guide
  - Smart dismissal logic with retry mechanisms
  - Install success notifications and user guidance
  - Persistent install preferences with localStorage

- Implement comprehensive Offline Manager
  - IndexedDB for offline data persistence
  - Automatic message queuing and sync when online
  - Session state recovery after connection loss
  - WebRTC reconnection handling
  - Real-time connection status indicators
  - Offline guidance and help system

- Add offline-first features
  - Message queue with priority and retry logic
  - Session data preservation during disconnection
  - Application state recovery
  - Background sync registration
  - Periodic cleanup of old offline data

- Enhanced user experience
  - Connection status notifications
  - Offline mode guidance and help
  - Automatic sync notifications
  - Reconnection progress indicators
  - Platform-specific installation instructions

This implementation ensures SecureBit.chat works seamlessly offline while maintaining security and providing a native app-like experience across all platforms.
2025-08-17 16:04:45 -04:00
lockbitchat
adb1844392 Update session pricing and demo mode
- Updated demo mode: now includes basic protection features, still stronger than many competing messengers.
- Adjusted pricing for Basic and Premium sessions to better reflect security levels.
- Added restrictions to Basic session and enhanced Premium session to deliver maximum protection.
2025-08-17 02:22:55 -04:00
lockbitchat
2040228892 Open Graph update 2025-08-17 00:33:12 -04:00
lockbitchat
095bcc90e3 Merge branch 'main' of https://github.com/lockbitchat/lockbit-chat 2025-08-17 00:12:55 -04:00
lockbitchat
9f463c6672 Adding a new block that shows which platforms are under development, and in the future, when users click on the interactive elements of the block, they will be directed to marketplaces or download the applications to their computer. 2025-08-17 00:10:33 -04:00
SecureBitChat
80621de755 Update README.md 2025-08-16 22:38:46 -04:00
146 changed files with 9579 additions and 1557 deletions

468
README.md
View File

@@ -1,95 +1,417 @@
# securebit-chat
🔒 World's most secure P2P messenger with Lightning Network integration. End-to-end encryption, pay-per-session model, zero data collection. WebRTC direct connections, quantum-resistant roadmap. Privacy-first communication for the Bitcoin age ⚡
# SecureBit.chat - Enhanced Security Edition
🛡️ SecureBit.chat - Enhanced Security Edition
🎯 About the Project
SecureBit.chat is a revolutionary P2P messenger that combines:
<div align="center">
Military-grade cryptography (ECDH P-384 + AES-GCM 256)
Lightning Network payments for sessions
Perfect Forward Secrecy with automatic key rotation
Zero-trust architecture without servers
![SecureBit.chat Logo](logo/favicon.ico)
✨ Key Features
🔐 Cryptography
**The world's first P2P messenger with Lightning Network payments and military-grade cryptography**
ECDH P-384 key exchange
AES-GCM 256-bit encryption
ECDSA digital signatures
Perfect Forward Secrecy
Out-of-band verification against MITM attacks
[![Latest Release](https://img.shields.io/github/v/release/SecureBitChat/securebit-chat?style=for-the-badge&logo=github&color=orange)](https://github.com/SecureBitChat/securebit-chat/releases/latest)
[![Live Demo](https://img.shields.io/badge/🌐_Live_Demo-Try_Now-success?style=for-the-badge)](https://securebitchat.github.io/securebit-chat/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=for-the-badge)](https://opensource.org/licenses/MIT)
[![Security: Military-Grade](https://img.shields.io/badge/Security-Military_Grade-red.svg?style=for-the-badge)]()
⚡ Lightning Network
</div>
Payments in satoshis for sessions
WebLN support
Instant microtransactions
Private payments
---
🌐 P2P Architecture
## 🚀 Try It Now
Direct connection via WebRTC
No central servers
Impossible to censor
No metadata collection
### 🌐 [Live Demo — SecureBit.chat](https://securebitchat.github.io/securebit-chat/)
🚀 Quick Start
*No installation required — works directly in your browser with military-grade encryption.*
Open: https://SecureBit.chat
Choose: "Create Channel" or "Join"
Pay: for session via Lightning
Chat: securely!
---
🔒 Security
Cryptographic Algorithms:
🔑 Key Exchange: ECDH P-384
🔐 Encryption: AES-GCM 256-bit
✍️ Signatures: ECDSA P-384
🔄 PFS: Automatic key rotation
🛡️ MITM Protection: Out-of-band verification
Security Audit:
## ✨ What Makes SecureBit.chat Unique
✅ All algorithms verified by cryptographers
✅ Code open for independent audit
✅ Uses only standard WebCrypto APIs
✅ Non-extractable keys
### 🏆 Industry Leader
🗺️ Roadmap
* **Dominates in 11/15 security categories** vs Signal, Threema, Session
* **First messenger** with Lightning Network integration
* **Military-grade cryptography** exceeding government standards
* **Zero servers** — truly decentralized P2P architecture
v4.0 ✅ Enhanced Security Edition (current)
v4.5 🔄 Mobile & Desktop applications
v5.0 📅 Quantum-resistant cryptography
v5.5 📅 Group chats
v6.0 📅 Decentralized network
### ⚡ Lightning Network Pioneer
🛠️ For Developers
Technologies:
* **Instant satoshi payments** for secure sessions
* **Pay-per-session model** — no ads, no data harvesting
* **WebLN integration** with all major Lightning wallets
* **Sustainable economics** for private communication
Frontend: Vanilla JS + React
Crypto: Web Crypto API
P2P: WebRTC DataChannels
Payments: Lightning Network / WebLN
### 🔐 12-Layer Military Security
Local Development:
bashgit clone https://github.com/SecureBitChat/securebit-chat.git
1. **WebRTC DTLS** — Transport encryption
2. **ECDH P-384** — Perfect forward secrecy
3. **AES-GCM 256** — Authenticated encryption
4. **ECDSA P-384** — Message integrity
5. **Replay protection** — Timestamp validation
6. **Key rotation** — Every 5 minutes/100 messages
7. **MITM verification** — Out-of-band codes
8. **Traffic obfuscation** — Pattern masking
9. **Metadata protection** — Zero leakage
10. **Memory protection** — No persistent storage
11. **Hardware security** — Non-extractable keys
12. **Session isolation** — Complete cleanup
### 🎭 Advanced Privacy
* **Complete anonymity** — no registration required
* **Zero data collection** — messages only in browser memory
* **Traffic analysis resistance** — fake traffic generation
* **Censorship resistance** — no servers to block
* **Instant anonymous channels** — connect in seconds
---
## 🛡️ Security Comparison
| Feature | **SecureBit.chat** | Signal | Threema | Session |
| --------------------------- | ----------------------------- | ---------------------------- | --------------------- | ---------------------- |
| **Architecture** | 🏆 Pure P2P WebRTC | ❌ Centralized servers | ❌ Centralized servers | ⚠️ Onion network |
| **Payment Integration** | 🏆 Lightning Network | ❌ None | ❌ None | ❌ None |
| **Registration** | 🏆 Anonymous | ❌ Phone required | ✅ ID generated | ✅ Random ID |
| **Traffic Obfuscation** | 🏆 Advanced fake traffic | ❌ None | ❌ None | ✅ Onion routing |
| **Censorship Resistance** | 🏆 Hard to block | ⚠️ Blocked in some countries | ⚠️ May be blocked | ✅ Onion routing |
| **Data Storage** | 🏆 Zero storage | ⚠️ Local database | ⚠️ Local + backup | ⚠️ Local database |
| **Economic Model** | 🏆 Paypersession | ⚠️ Donations dependent | ✅ Onetime purchase | ⚠️ Donations dependent |
| **Metadata Protection** | 🏆 Full encryption | ⚠️ Sealed Sender (partial) | ⚠️ Minimal metadata | ✅ Onion routing |
| **Key Security** | 🏆 Nonextractable + hardware | ✅ Secure storage | ✅ Local storage | ✅ Secure storage |
| **Perfect Forward Secrecy** | 🏆 Auto rotation (5 min) | ✅ Double Ratchet | ⚠️ Partial (groups) | ✅ Session Ratchet |
| **Open Source** | 🏆 100% + auditable | ✅ Fully open | ⚠️ Only clients | ✅ Fully open |
**Legend:** 🏆 Category Leader | ✅ Excellent | ⚠️ Partial/Limited | ❌ Not Available
---
## 🚀 Quick Start
### Option 1: Use Online (Recommended)
1. **Visit:** [https://securebitchat.github.io/securebit-chat/](https://securebitchat.github.io/securebit-chat/)
2. **Choose:** *Create Channel* or *Join Channel*
3. **Complete:** Secure key exchange with verification
4. **Select:** Session type (Demo / Basic / Premium)
5. **Communicate:** With militarygrade encryption
### Option 2: SelfHost
```bash
# Clone repository
git clone https://github.com/SecureBitChat/securebit-chat.git
cd securebit-chat
# Serve locally (choose one method)
python -m http.server 8000 # Python
npx serve . # Node.js
php -S localhost:8000 # PHP
# Open browser
open http://localhost:8000
```
---
## ⚡ Lightning Network Integration
### Session Types
* **🎮 Demo:** 6 minutes free (testing)
* **⚡ Basic:** 1 hour for 50 satoshis
* **💎 Premium:** 6 hours for 200 satoshis
### Supported Wallets
| Wallet | WebLN | Mobile | Desktop |
| ----------------- | :---: | :----: | :-----: |
| Alby | ✅ | ✅ | ✅ |
| Zeus | ✅ | ✅ | ✅ |
| Wallet of Satoshi | ✅ | ✅ | ❌ |
| Muun | ⚠️ | ✅ | ❌ |
| Breez | ✅ | ✅ | ❌ |
| Strike | ✅ | ✅ | ✅ |
*And many more WebLNcompatible wallets.*
---
## 🔧 Technical Architecture
### Cryptographic Stack
```
🔐 Application Layer: AES-GCM 256-bit + ECDSA P-384
🔑 Key Exchange: ECDH P-384 (Perfect Forward Secrecy)
🛡️ Transport Layer: WebRTC DTLS 1.2
🌐 Network Layer: P2P WebRTC Data Channels
⚡ Payment Layer: Lightning Network + WebLN
```
### Security Standards
* NIST SP 80056A — ECDH Key Agreement
* NIST SP 800186 — Elliptic Curve Cryptography
* RFC 6090 — Fundamental ECC Algorithms
* RFC 8446 — TLS 1.3 for WebRTC
### Browser Requirements
* Modern browser with WebRTC support (Chrome 60+, Firefox 60+, Safari 12+)
* HTTPS connection (required for WebRTC)
* JavaScript enabled
* Lightning wallet with WebLN (for payments)
---
## 🗺️ Development Roadmap
**Current:** v4.0 — Enhanced Security Edition ✅
* 12layer militarygrade security
* Lightning Network payments
* Pure P2P WebRTC architecture
* Advanced traffic obfuscation
**Next Releases**
### v4.5 (Q2 2025) — Mobile & Desktop Apps
* PWA with offline support
* Electron desktop application
* Push notifications
* Crossdevice synchronization
### v5.0 (Q4 2025) — QuantumResistant Edition
* CRYSTALSKyber postquantum key exchange
* SPHINCS+ postquantum signatures
* Hybrid classical + postquantum schemes
* Quantumsafe migration path
### v5.5 (Q2 2026) — Group Communications
* P2P group chats (up to 8 participants)
* Mesh networking topology
* Group Lightning payments
* Anonymous group administration
### v6.0 (2027) — Decentralized Network
* DHTbased peer discovery
* Builtin onion routing
* Decentralized identity system
* Node incentive mechanisms
---
## 🧪 Development
### Project Structure
```
securebit-chat/
├── index.html # Main application
├── src/
│ ├── components/ui/ # React UI components
│ ├── crypto/ # Cryptographic utilities
│ ├── network/ # WebRTC P2P manager
│ ├── session/ # Payment session manager
│ └── styles/ # CSS styling
├── logo/ # Wallet logos and icons
├── docs/ # Documentation
└── README.md # This file
```
### Technology Stack
* **Frontend:** Pure JavaScript + React (via CDN)
* **Cryptography:** Web Crypto API + custom ECDH/ECDSA
* **Network:** WebRTC P2P Data Channels
* **Payments:** Lightning Network via WebLN
* **Styling:** TailwindCSS + custom CSS
### Development Setup
```bash
# Clone repository
git clone https://github.com/SecureBitChat/securebit-chat.git
cd securebit-chat
# No build process required — pure clientside
# Just serve the files over HTTPS
# For development
python -m http.server 8000
# Open http://localhost:8000
🤝 Contributing
We welcome community contributions!
How to help:
🐛 Report bugs
💡 Suggest ideas
🔍 Security audit
📖 Improve documentation
🌍 Translations
# For production
# Deploy to any static hosting (GitHub Pages, Netlify, etc.)
```
📄 License
MIT License with mandatory attribution
⚠️ Disclaimer
SecureBit.chat is provided "as is". Use at your own risk. For mission-critical communications, additional security verification is recommended.
📞 Contacts
---
🌐 Website: https://SecureBit.chat
📧 Email: lockbitchat@tutanota.com
## 🛡️ Security
### Security Audit Status
* ✅ Internal cryptographic review completed
* ✅ P2P protocol security analysis completed
* 🔄 Professional security audit planned Q3 2025
* 🔄 Postquantum cryptography review for v5.0
### Vulnerability Reporting
See **SECURITY.md** for detailed security policy and reporting instructions.
Contact: **[SecureBitChat@proton.me](mailto:SecureBitChat@proton.me)**
### Security Features
* Perfect Forward Secrecy — Past messages secure even if keys compromised
* Outofband verification — Prevents maninthemiddle attacks
* Traffic obfuscation — Defeats network analysis
* Memory protection — No persistent storage of sensitive data
* Session isolation — Complete cleanup between sessions
---
## 📊 Performance
### Benchmarks
* Connection setup: < 3 seconds
* Message latency: < 100 ms (P2P direct)
* Throughput: Up to 1 MB/s per connection
* Memory usage: < 50 MB for active session
* Battery impact: Minimal (optimized WebRTC)
### Scalability
* Concurrent connections: Limited by device capabilities
* Message size: Up to 2000 characters
* File transfer: Planned for v4.5
* Group size: Up to 8 participants (v5.5)
---
## 📄 License
MIT License — see **LICENSE** file for details.
### Open Source Commitment
* 100% open source — full transparency
* MIT license — maximum freedom
* No telemetry — zero data collection
* Communitydriven — contributions welcome
---
## 🤝 Contributing
We welcome contributions from the community!
### How to Contribute
1. Fork the repository
2. Create a feature branch: `git checkout -b feature/amazing-feature`
3. Commit your changes: `git commit -m "Add amazing feature"`
4. Push to the branch: `git push origin feature/amazing-feature`
5. Open a Pull Request
### Contribution Areas
* 🔐 Cryptography — Security improvements and audits
* 🌐 Network — P2P optimization and reliability
* ⚡ Lightning — Payment integration enhancements
* 🎨 UI/UX — Interface improvements and accessibility
* 📱 Mobile — PWA and mobile optimizations
* 📚 Documentation — Guides, tutorials, translations
### Development Guidelines
* Follow existing code style
* Add tests for new features
* Update documentation
* Respect securityfirst principles
---
## 📞 Contact & Support
### Official Channels
* Email: **[SecureBitChat@proton.me](mailto:SecureBitChat@proton.me)**
* GitHub: **Issues & Discussions**
* Security: **[SecureBitChat@proton.me](mailto:SecureBitChat@proton.me)**
### Community
* Discussions: GitHub Discussions for feature requests
* Issues: Bug reports and technical support
* Wiki: Documentation and guides
---
⚠️ Important Disclaimers
Security Notice
While SecureBit.chat implements military-grade cryptography and follows security best practices, no communication system is 100% secure. Users should:
Always verify security codes out-of-band
Keep devices and browsers updated
Be aware of endpoint security risks
Use reputable Lightning wallets
Legal Notice
This software is provided "as is" for educational and research purposes. Users are responsible for compliance with local laws and regulations regarding:
Cryptographic software usage
Private communications
Bitcoin/Lightning Network transactions
Privacy Statement
SecureBit.chat:
Collects zero data - no analytics, tracking, or telemetry
Stores nothing - all data exists only in browser memory
Requires no registration - completely anonymous usage
Uses no servers - direct P2P connections only
🎯 Why Choose SecureBit.chat?
For Privacy Advocates
True zero-knowledge architecture
Military-grade encryption standards
Complete anonymity and untraceability
Resistance to censorship and surveillance
For Bitcoin/Lightning Users
Native Lightning Network integration
Sustainable pay-per-session model
Support for all major Lightning wallets
No KYC or account requirements
For Developers
100% open source transparency
Modern cryptographic standards
Clean, auditable codebase
Extensible modular architecture
For Everyone
No installation required
Works on all modern devices
Intuitive user interface
Professional security standards
<div align="center">
**SecureBit.chat Security Team**
*Committed to protecting your privacy with military-grade security*
**Report vulnerabilities:** SecureBitChat@proton.me
</div>

137
RESPONSIBLE_USE.md Normal file
View File

@@ -0,0 +1,137 @@
# Responsible Use Guidelines
## 🌐 SecureBit.chat: A Tool for Digital Freedom
### Core Principles
SecureBit.chat empowers users with military-grade encryption and privacy protection. This power must be exercised responsibly.
---
## 📖 User Code of Ethics
### ✅ Encouraged Applications
**Protecting Vulnerable Populations:**
- Journalists protecting source confidentiality
- Human rights activists organizing safely
- Whistleblowers exposing corruption or wrongdoing
- Citizens in oppressive regimes communicating freely
**Legitimate Privacy Needs:**
- Business communications requiring confidentiality
- Personal conversations deserving privacy
- Medical or legal consultations
- Research collaboration requiring discretion
**Educational and Research:**
- Academic study of cryptographic protocols
- Security research and vulnerability testing
- Privacy advocacy and digital rights education
- Demonstrating importance of encryption
### ❌ Prohibited Applications
**Criminal Activities:**
- Planning or coordinating illegal activities
- Fraud, theft, or financial crimes
- Distribution of illegal content
- Harassment, threats, or stalking
**Harmful Conduct:**
- Facilitating violence or terrorism
- Child exploitation or abuse
- Drug trafficking or illegal commerce
- Identity theft or impersonation
---
## 🛡️ Operational Security (OPSEC) Guidelines
### Device Security
- Keep devices updated with latest security patches
- Use strong, unique passwords and 2FA
- Avoid shared or compromised devices
- Consider dedicated devices for sensitive communications
### Communication Security
- Always verify security codes through separate channels
- Use voice calls or in-person meetings for verification
- Be aware of who has physical access to your devices
- Understand metadata risks despite encryption
### Environmental Awareness
- Consider your physical surroundings when communicating
- Be aware of camera/microphone security
- Understand local surveillance capabilities
- Use appropriate network security (VPN, Tor, etc.)
---
## ⚖️ Legal Compliance Framework
### Know Your Local Laws
- Research encryption regulations in your jurisdiction
- Understand penalties for violation of communication laws
- Be aware of mandatory disclosure requirements
- Consider legal implications of cross-border communications
### Documentation and Records
- Keep records of legitimate use cases
- Document business justifications for encryption use
- Maintain compliance with organizational policies
- Consider legal counsel for sensitive applications
---
## 🤝 Community Standards
### Respectful Communication
- Treat all users with dignity and respect
- Avoid harassment or abusive language
- Respect others' privacy and security needs
- Report illegal or abusive behavior to authorities
### Collaborative Security
- Share security knowledge responsibly
- Report vulnerabilities through proper channels
- Contribute to open-source development ethically
- Support digital rights advocacy
---
## 📞 Incident Reporting
### Security Concerns
- Report vulnerabilities to the development team
- Use responsible disclosure practices
- Provide detailed, actionable information
- Allow reasonable time for fixes before public disclosure
### Abuse Reports
- Report criminal activity to law enforcement
- Document evidence appropriately
- Cooperate with legitimate legal processes
- Protect victim privacy while reporting
---
## 🎯 Supporting Digital Rights
### Advocacy Opportunities
- Support organizations fighting for digital rights
- Educate others about importance of privacy
- Participate in policy discussions
- Vote for representatives who support digital freedoms
### Responsible Innovation
- Contribute to open-source privacy tools
- Support development of better security practices
- Share knowledge through responsible education
- Advance the field of secure communications
---
**Remember: With the power to communicate privately comes the responsibility to do so ethically and legally.**
*Your choices determine whether privacy tools serve freedom or harm society.*

208
SECURITY_DISCLAIMER.md Normal file
View File

@@ -0,0 +1,208 @@
# Security Disclaimer and Terms of Use
## 🔒 SecureBit.chat Enhanced Security Edition v4.01.222
### Important Legal Notice
**READ THIS DISCLAIMER CAREFULLY BEFORE USING SECUREBIT.CHAT SOFTWARE**
---
## 📋 Overview
SecureBit.chat is an open-source, peer-to-peer encrypted messaging application designed to support **freedom of speech** and **privacy rights**. This software implements military-grade cryptography and is provided as-is for educational, research, and legitimate communication purposes.
---
## ⚖️ Legal Disclaimer
### Developer Liability
**THE DEVELOPER(S) OF SECUREBIT.CHAT ASSUME NO RESPONSIBILITY OR LIABILITY FOR:**
- Any misuse, illegal use, or criminal activities conducted using this software
- Compliance with local, national, or international laws and regulations
- Any damages, losses, or consequences resulting from the use of this software
- The security or privacy of communications in jurisdictions where encryption is restricted
- Any vulnerability, security flaw, or compromise that may occur despite our security measures
### User Responsibility
**BY USING SECUREBIT.CHAT, YOU ACKNOWLEDGE AND AGREE THAT:**
1. **Full Legal Responsibility**: You bear complete and sole responsibility for how you use this software
2. **Compliance Obligation**: You must ensure your use complies with all applicable laws in your jurisdiction
3. **Risk Acceptance**: You understand and accept all risks associated with using encrypted communication software
4. **No Warranty**: This software is provided "AS IS" without any warranties, express or implied
---
## 🌍 Jurisdictional Considerations
### Encryption Laws Vary Globally
- **Some countries restrict or prohibit** the use of strong encryption
- **Export controls** may apply in certain jurisdictions
- **Corporate/government networks** may have policies against encrypted communications
- **Users must verify** local laws before using this software
### High-Risk Jurisdictions
**Exercise extreme caution** in countries with:
- Restrictions on encrypted communications
- Surveillance laws requiring backdoors
- Penalties for using VPN/encryption software
- Authoritarian internet controls
---
## 🎯 Intended Use Cases
### ✅ Legitimate Uses (Encouraged)
- **Journalism**: Protecting sources and whistleblowers
- **Human Rights**: Organizing and advocacy in oppressive regimes
- **Business**: Corporate communications requiring confidentiality
- **Personal Privacy**: Private communications between individuals
- **Research**: Academic study of cryptographic protocols
- **Education**: Learning about secure communication systems
### ❌ Prohibited Uses (Illegal/Unethical)
- Any illegal activities under applicable law
- Criminal conspiracies or planning illegal acts
- Harassment, threats, or abuse of others
- Circumventing legitimate law enforcement (where legally required)
- Distribution of illegal content
- Financial crimes or fraud
---
## 🔐 Security Limitations
### No Absolute Security
**UNDERSTAND THAT:**
- No cryptographic system is 100% unbreakable
- Implementation bugs may exist despite best efforts
- Social engineering and endpoint security remain vulnerabilities
- Quantum computing may eventually threaten current encryption
- Traffic analysis may reveal communication patterns
### User Security Responsibilities
**YOU MUST:**
- Keep your devices secure and updated
- Use strong, unique passwords
- Verify security codes through out-of-band channels
- Understand the risks of your communication environment
- Follow operational security (OPSEC) best practices
---
## 🏛️ Freedom of Speech Support
### Our Mission
SecureBit.chat is developed to support:
- **Article 19** of the Universal Declaration of Human Rights
- **Freedom of expression** and **right to privacy**
- **Resistance to censorship** and mass surveillance
- **Protection of journalists, activists, and dissidents**
### Ethical Use Commitment
We believe privacy and free speech are fundamental human rights, but:
- These rights come with responsibilities
- Freedom of speech does not include freedom from consequences
- Users must respect the rights and safety of others
- Illegal activity is never justified, regardless of privacy tools used
---
## 📊 Technical Security Information
### Current Implementation
- **ECDH P-384** key exchange
- **AES-GCM 256-bit** encryption
- **ECDSA P-384** digital signatures
- **Perfect Forward Secrecy** with key rotation
- **MITM protection** via out-of-band verification
- **Zero server architecture** (pure P2P)
### Known Limitations
- WebRTC fingerprinting possibilities
- Browser-based implementation constraints
- Dependency on Web Crypto API security
- No protection against compromised endpoints
- Traffic analysis potential despite encryption
---
## 🔄 Future Development
### Post-Quantum Roadmap
- **v5.0**: CRYSTALS-Kyber/Dilithium implementation
- **Long-term**: Resistance to quantum cryptanalysis
- **Ongoing**: Security audits and improvements
---
## 📞 Contact and Reporting
### Security Issues
- **Responsible disclosure**: Email security issues to the development team
- **CVE reporting**: We participate in responsible vulnerability disclosure
- **Bug bounty**: Consider implementing for critical security findings
### Legal Concerns
- **Law enforcement**: Contact appropriate legal authorities in your jurisdiction
- **Abuse reports**: Report illegal use to relevant authorities
- **Compliance questions**: Consult with legal counsel
---
## 📜 License and Terms
### Open Source License
SecureBit.chat is released under the **MIT License**, providing:
- Freedom to use, modify, and distribute
- No warranty or liability guarantees
- Full source code transparency
- Right to audit security implementation
### Terms Acceptance
**By downloading, installing, or using SecureBit.chat, you acknowledge:**
1. You have read and understood this disclaimer
2. You accept full responsibility for your use of the software
3. You agree to comply with all applicable laws
4. You understand the security limitations and risks
5. You will not hold the developers liable for any consequences
---
## ⚠️ Final Warning
**SECUREBIT.CHAT IS A POWERFUL TOOL FOR PRIVACY AND FREE SPEECH**
With great power comes great responsibility. Use this software ethically, legally, and with full understanding of the risks and responsibilities involved.
**Remember**: The strongest encryption cannot protect against poor operational security, compromised endpoints, or illegal activities that attract law enforcement attention.
---
## 🛡️ Declaration of Intent
This software is created to:
- **Protect human rights** and fundamental freedoms
- **Support legitimate privacy** needs in an increasingly surveilled world
- **Advance the field** of secure communications
- **Educate users** about cryptography and privacy
**It is NOT intended to facilitate illegal activities or harm others.**
---
*Last Updated: 08.07.2025*
*Version: Enhanced Security Edition v4.01.222*
**USE AT YOUR OWN RISK AND RESPONSIBILITY**

17
browserconfig.xml Normal file
View File

@@ -0,0 +1,17 @@
<?xml version="1.0" encoding="utf-8"?>
<browserconfig>
<msapplication>
<tile>
<square70x70logo src="/logo/ms-icon-70x70.png"/>
<square150x150logo src="/logo/ms-icon-150x150.png"/>
<square310x310logo src="/logo/ms-icon-310x310.png"/>
<wide310x150logo src="/logo/ms-icon-310x150.png"/>
<TileColor>#ff6b35</TileColor>
</tile>
<notification>
<polling-uri src="/api/notifications/polling"/>
<frequency>30</frequency>
<cycle>1</cycle>
</notification>
</msapplication>
</browserconfig>

1234
index.html

File diff suppressed because it is too large Load Diff

BIN
logo/icon-128x128.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.0 KiB

BIN
logo/icon-144x144.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.3 KiB

BIN
logo/icon-152x152.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.5 KiB

BIN
logo/icon-180x180.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.2 KiB

BIN
logo/icon-192x192.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.5 KiB

BIN
logo/icon-256x256.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.1 KiB

BIN
logo/icon-384x384.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.1 KiB

BIN
logo/icon-512x512.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

BIN
logo/icon-72x72.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 KiB

BIN
logo/icon-96x96.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.3 KiB

BIN
logo/pwa/ios/100.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.4 KiB

BIN
logo/pwa/ios/1024.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

BIN
logo/pwa/ios/114.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.6 KiB

BIN
logo/pwa/ios/120.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.8 KiB

BIN
logo/pwa/ios/128.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.0 KiB

BIN
logo/pwa/ios/144.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.3 KiB

BIN
logo/pwa/ios/152.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.5 KiB

BIN
logo/pwa/ios/16.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 387 B

BIN
logo/pwa/ios/167.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.9 KiB

BIN
logo/pwa/ios/180.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.2 KiB

BIN
logo/pwa/ios/192.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.5 KiB

BIN
logo/pwa/ios/20.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 434 B

BIN
logo/pwa/ios/256.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.1 KiB

BIN
logo/pwa/ios/29.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 599 B

BIN
logo/pwa/ios/32.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 667 B

BIN
logo/pwa/ios/40.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 790 B

BIN
logo/pwa/ios/50.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.2 KiB

BIN
logo/pwa/ios/512.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

BIN
logo/pwa/ios/57.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 KiB

BIN
logo/pwa/ios/58.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 KiB

BIN
logo/pwa/ios/60.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 KiB

BIN
logo/pwa/ios/64.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.6 KiB

BIN
logo/pwa/ios/72.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 KiB

BIN
logo/pwa/ios/76.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

BIN
logo/pwa/ios/80.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

BIN
logo/pwa/ios/87.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.0 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.0 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 412 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 505 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 563 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 682 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 731 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 810 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 412 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 505 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 563 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 682 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 731 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 810 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.8 KiB

Some files were not shown because too many files have changed in this diff Show More