w3mypq

The size of the files that can be encrypted depends entirely on the processor power and RAM of the device running the browser. Remember, all file encryption and decryption happen directly client-side within the browser. Furthermore, while you can easily encrypt files to create a 500MB or even 1GB payload, you must also account for connection speeds and the server's capacity to handle uploading or downloading such large amounts of data.

The plugin allows users to encrypt files locally in their browser before sharing or storing them. It supports post-quantum key encapsulation using ML-KEM and digital signatures using ML-DSA. Encrypted files can be shared with recipients who decrypt them locally using their own private keys.

Registered users can encrypt files for one or more recipients. Recipients receive access information and can decrypt the files locally using their corresponding Private keys once downloaded.

No. Private keys are generated locally in the user's browser and should be stored securely by the user. The server only stores information necessary for sharing encrypted content, such as public keys and encrypted files.

ML-KEM and ML-DSA are NIST-standardized post-quantum cryptographic algorithms. ML-KEM handles secure key exchange, and ML-DSA provides digital signatures and sender verification. AES-GCM is the symmetric encryption algorithm used to encrypt and decrypt the bulk file data itself, ensuring high-speed authenticated encryption.

Guest mode allows visitors to perform encryption and decryption locally without creating an account. Files do not need to be uploaded to the server when using guest mode.

The plugin includes a compiled version of the Noble post-quantum cryptography library for ML-KEM and ML-DSA.

• Noble