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:
@@ -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