Search Results for "sha256"

Petoron P2P Messenger (P-P2P-M) Architecture: Pure P2P - no servers, no databases Key storage: Keys generated in memory, never stored, erased after use Metadata: Only IP and port exist during the session - everything else is encrypted & obfuscated Encryption: PQS v1.2 - PBKDF2-HMAC-SHA256 (200k), BLAKE2s-MAC, custom stream cipher + fake padding Authentication: BLAKE2s-MAC (16 bytes) - instant failure on any data change Packet obfuscation: --stealth mode - padding, hidden structures Connection: Direct peer-to-peer only Anonymity: No accounts, logins, or phone numbers Third-party access: Impossible without physical access to both peers during session History: No storage — all in RAM, wiped on close Message size: Limited only by RAM & MTU — no artificial limits External dependencies: None DPI/blocking resistance: Harder to detect, can be masked Autonomy: Fully offline until peers connect 26.01.26 Add pqs_chat_tor.py github.com/01alekseev/Petoron-P2P-Messenger

Please go to https://github.com/eidheim/Simple-WebSocket-Server, as this sourceforge page will no longer be updated.

...You can chat with other peers in clear text or AES password-based encryption on your own computer network. The AES encryption and decryption is based on 128 bit key which is reached by padding the resulting SHA256 from your provided password. Simply put, SHA is a checksum that change when a single bit change. When you send a message with a password field, the resulting password checksum is cut at 128 bit which means 16 characters bytes KEY is entered into AES 128 bit encryption and decryption scheme. The resulting ciphertext is sent to the server while the server relay it to the connected peers. ...