Search Results for "ram"

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

Petoron Crypto Archiver (PCA) Key features: AES-256-CFB encryption with unique IV per archive Argon2id key derivation (256MB RAM / time_cost=3 / parallelism=4) HMAC-SHA512 integrity and anti-tampering check No compression, no fingerprinting, no trace of original data Works with both single files and entire directories Fully CLI-based, portable, and open format (.pca) https://github.com/01alekseev/PCA

A version of Midbar data vault adapted for the ESP32 CYD and WebFlash. It keeps the cryptographic keys in the ESP32 RAM and stores the ciphertexts (encrypted data) in the Google Firebase. The tutorial is available at: https://www.instructables.com/How-to-Turn-ESP32-CYD-Into-a-Secure-IoT-Data-Vault/ WebFlash for ESP32-CYD: https://northstrix.github.io/Midbar-ESP32-CYD-Firebase-Edition/flash WebFlash for ESP32-CYD2USB: https://northstrix.github.io/Midbar-ESP32-CYD2USB-Firebase-Edition/flash

Petoron Time Burn Cipher (PTBC) A promising cipher based on self-destruction of time, complete absence of traces and impossibility of key selection. Key features: AES-CFB encryption with per-file IV Argon2id key derivation with 256MB RAM resistance TTL (time to live) built directly into the encrypted file HMAC-SHA512 integrity verification Self-deleting mode (--autowipe) and one-time access marking (--onetime) No file metadata, no recovery, no password resets Philosophy: If you lose the password - it’s over. If time expires - it’s gone. PTBC doesn’t forgive, doesn’t forget, and doesn’t leak. ...

...See the documentation for more informations and an example of use: https://sourceforge.net/p/proxycrypt/doc/ Requirements: - Windows 7 or later - Arsenal Image Mounter or ImDisk Virtual Disk Driver - Administrative privileges - 64-bit CPU with SSE3 instructions - About 1 GB of RAM temporarily required for password checking with default settings Hashes of all versions: https://sourceforge.net/p/proxycrypt/doc/Hash