feat: rebrand to SecureBit.chat due to name conflict
BREAKING CHANGE: Project renamed from LockBit.chat to SecureBit.chat - Changed project name to avoid confusion with LockBit ransomware group - Updated all documentation, branding, and references - Maintained all existing functionality and security features - Domain migration planned to securebit.chat Reason: The LockBit name became associated with a notorious ransomware group, causing conflicts on platforms and potential confusion for users. SecureBit better reflects our mission of providing secure P2P messaging while avoiding negative associations. This change affects: - README.md and all documentation - Package.json name field - Brand assets and logos - Website references - Social media handles Core functionality remains unchanged: ✅ 12-layer military-grade security ✅ Lightning Network integration ✅ P2P WebRTC architecture ✅ Open source MIT license
This commit is contained in:
lockbitchat
@@ -1,8 +1,8 @@
|
||||
# LockBit.chat API Documentation
|
||||
# SecureBit.chat API Documentation
|
||||
|
||||
## 🏗️ Architecture Overview
|
||||
|
||||
LockBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
|
||||
SecureBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
|
||||
|
||||
## 📚 Core Classes
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Contributing to LockBit.chat
|
||||
# Contributing to SecureBit.chat
|
||||
|
||||
🎉 **Thank you for your interest in contributing to LockBit.chat!**
|
||||
🎉 **Thank you for your interest in contributing to SecureBit.chat!**
|
||||
|
||||
We're building the most secure P2P messenger with Lightning Network integration, and we need your help to make it even better.
|
||||
|
||||
@@ -19,7 +19,7 @@ Help audit our cryptographic implementation
|
||||
Improve guides, tutorials, and technical docs
|
||||
|
||||
### 🌍 Translations
|
||||
Help make LockBit.chat accessible worldwide
|
||||
Help make SecureBit.chat accessible worldwide
|
||||
|
||||
### 💻 Code Contributions
|
||||
Submit pull requests for bug fixes and features
|
||||
@@ -36,8 +36,8 @@ Submit pull requests for bug fixes and features
|
||||
``bash
|
||||
# 1. Fork the repository on GitHub
|
||||
# 2. Clone your fork
|
||||
git clone https://github.com/yourusername/lockbit-chat.git
|
||||
cd lockbit-chat
|
||||
git clone https://github.com/yourusername/securebit-chat.git
|
||||
cd securebit-chat
|
||||
|
||||
# 3. Create a development branch
|
||||
git checkout -b feature/your-feature-name
|
||||
@@ -240,7 +240,7 @@ Submit PR - Follow contribution guidelines
|
||||
|
||||
Translation Keys
|
||||
json{
|
||||
"header.title": "LockBit.chat - Enhanced Security Edition",
|
||||
"header.title": "SecureBit.chat - Enhanced Security Edition",
|
||||
"security.level.high": "HIGH",
|
||||
"crypto.algorithm.ecdh": "ECDH P-384",
|
||||
"error.connection.failed": "Connection failed"
|
||||
@@ -267,7 +267,7 @@ Communication Channels
|
||||
GitHub Discussions - Technical discussions
|
||||
GitHub Issues - Bug reports and features
|
||||
Email - lockbitchat@tutanota.com
|
||||
Security - security@lockbit.chat
|
||||
Security - security@SecureBit.chat
|
||||
|
||||
Code of Conduct
|
||||
We follow the Contributor Covenant:
|
||||
@@ -311,11 +311,11 @@ Thank you for helping make the internet more private and secure! 🛡️
|
||||
# docs/API.md
|
||||
|
||||
``markdown
|
||||
# LockBit.chat API Documentation
|
||||
# SecureBit.chat API Documentation
|
||||
|
||||
## 🏗️ Architecture Overview
|
||||
|
||||
LockBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
|
||||
SecureBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
|
||||
|
||||
## 📚 Core Classes
|
||||
|
||||
@@ -954,7 +954,7 @@ javascript// Service worker for offline capability
|
||||
// sw.js
|
||||
self.addEventListener('install', event => {
|
||||
event.waitUntil(
|
||||
caches.open('lockbit-chat-v1').then(cache => {
|
||||
caches.open('securebit-chat-v1').then(cache => {
|
||||
return cache.addAll([
|
||||
'/',
|
||||
'/index.html',
|
||||
@@ -1203,7 +1203,7 @@ Getting Help
|
||||
Documentation: Full API docs at /docs/
|
||||
GitHub Issues: Bug reports and feature requests
|
||||
Community: Discussions and Q&A
|
||||
Security: security@lockbit.chat for vulnerabilities
|
||||
Security: security@SecureBit.chat for vulnerabilities
|
||||
|
||||
Contributing
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# LockBit.chat Cryptographic Implementation
|
||||
# SecureBit.chat Cryptographic Implementation
|
||||
|
||||
## 🔐 Overview
|
||||
|
||||
LockBit.chat implements state-of-the-art cryptographic protocols providing **military-grade security** for peer-to-peer communications. Our cryptographic design prioritizes security, performance, and future-proofing against emerging threats including quantum computing.
|
||||
SecureBit.chat implements state-of-the-art cryptographic protocols providing **military-grade security** for peer-to-peer communications. Our cryptographic design prioritizes security, performance, and future-proofing against emerging threats including quantum computing.
|
||||
|
||||
**Cryptographic Strength:** 256+ bit security level
|
||||
**Quantum Resistance:** Timeline > 2040
|
||||
@@ -492,7 +492,7 @@ async function deriveSharedKeys(privateKey, publicKey, salt) {
|
||||
const encoder = new TextEncoder();
|
||||
|
||||
// Enhanced context info
|
||||
const contextInfo = encoder.encode('LockBit.chat v4.0 Enhanced Security Edition');
|
||||
const contextInfo = encoder.encode('SecureBit.chat v4.0 Enhanced Security Edition');
|
||||
|
||||
// Derive master shared secret
|
||||
const sharedSecret = await crypto.subtle.deriveKey(
|
||||
@@ -1302,9 +1302,9 @@ class CryptographicErrorHandler {
|
||||
### Technical Support
|
||||
|
||||
For cryptographic implementation questions:
|
||||
- **Security Team:** security@lockbit.chat
|
||||
- **Cryptographic Specialists:** crypto@lockbit.chat
|
||||
- **GitHub Issues:** [Cryptography Issues](https://github.com/lockbitchat/lockbit-chat/issues?q=label%3Acryptography)
|
||||
- **Security Team:** security@SecureBit.chat
|
||||
- **Cryptographic Specialists:** crypto@SecureBit.chat
|
||||
- **GitHub Issues:** [Cryptography Issues](https://github.com/lockbitchat/securebit-chat/issues?q=label%3Acryptography)
|
||||
|
||||
### Additional Resources
|
||||
|
||||
@@ -1327,7 +1327,7 @@ For cryptographic implementation questions:
|
||||
|
||||
## 🏁 Conclusion
|
||||
|
||||
LockBit.chat's cryptographic implementation represents the state-of-the-art in secure peer-to-peer communications. Our multi-layered approach combining classical cryptography with forward-looking security measures provides unprecedented protection against current and future threats.
|
||||
SecureBit.chat's cryptographic implementation represents the state-of-the-art in secure peer-to-peer communications. Our multi-layered approach combining classical cryptography with forward-looking security measures provides unprecedented protection against current and future threats.
|
||||
|
||||
### Key Achievements
|
||||
|
||||
@@ -1348,11 +1348,11 @@ Our cryptographic implementation provides:
|
||||
- **Forward Secrecy:** Past communications remain secure
|
||||
- **Replay Protection:** Comprehensive anti-replay mechanisms
|
||||
|
||||
**This cryptographic foundation enables LockBit.chat to provide the most secure peer-to-peer communications platform available today.**
|
||||
**This cryptographic foundation enables SecureBit.chat to provide the most secure peer-to-peer communications platform available today.**
|
||||
|
||||
---
|
||||
|
||||
*This document reflects the current state of cryptographic implementation in LockBit.chat v4.0. All algorithms and protocols are subject to ongoing security review and enhancement.*
|
||||
*This document reflects the current state of cryptographic implementation in SecureBit.chat v4.0. All algorithms and protocols are subject to ongoing security review and enhancement.*
|
||||
|
||||
**Last Updated:** January 14, 2025
|
||||
**Document Version:** 4.0
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# LockBit.chat Security Architecture
|
||||
# SecureBit.chat Security Architecture
|
||||
|
||||
## 🛡️ Overview
|
||||
|
||||
LockBit.chat implements a revolutionary **12-layer security architecture** that provides military-grade protection for peer-to-peer communications. This document details the technical implementation of our security system, which exceeds most government and enterprise communication standards.
|
||||
SecureBit.chat implements a revolutionary **12-layer security architecture** that provides military-grade protection for peer-to-peer communications. This document details the technical implementation of our security system, which exceeds most government and enterprise communication standards.
|
||||
|
||||
**Current Implementation:** Stage 4 - Maximum Security
|
||||
**Security Rating:** Military-Grade
|
||||
@@ -107,7 +107,7 @@ const keyPackage = {
|
||||
- **Curve:** NIST P-384 (secp384r1)
|
||||
- **Key Derivation:** HKDF with SHA-384
|
||||
- **Salt Size:** 64 bytes (enhanced from standard 32 bytes)
|
||||
- **Context Info:** "LockBit.chat v4.0 Enhanced Security Edition"
|
||||
- **Context Info:** "SecureBit.chat v4.0 Enhanced Security Edition"
|
||||
|
||||
**Key Derivation Process:**
|
||||
```javascript
|
||||
@@ -706,9 +706,9 @@ webrtcManager.checkFakeTrafficStatus()
|
||||
|
||||
For technical questions about the security architecture:
|
||||
|
||||
- **Security Team:** security@lockbit.chat
|
||||
- **Technical Documentation:** docs@lockbit.chat
|
||||
- **GitHub Issues:** [Security Architecture Issues](https://github.com/lockbitchat/lockbit-chat/issues?q=label%3Asecurity-architecture)
|
||||
- **Security Team:** security@SecureBit.chat
|
||||
- **Technical Documentation:** docs@SecureBit.chat
|
||||
- **GitHub Issues:** [Security Architecture Issues](https://github.com/lockbitchat/securebit-chat/issues?q=label%3Asecurity-architecture)
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user