Currently, we support raw text strings, JSON strings, and most basic configuration files such as .yml and .json.
Deadrop leverages a variation of the AES algorithm and verifies integrity by computing and comparing SHA-256 hash signatures.
Neither public nor private keys are ever persisted on disk anywhere. Key pairs are kept in-memory only during the lifetime of the session and are immediately destroyed upon completion. They are also never sent to any servers or APIs, only being transmitted over secure peer-to-peer WebRTC connections.
There can only be one dropper (sender) and one grabber (receiver) within a deadrop session. Support for multi-user drops is in the roadmap as a premium feature.
The first stable iteration of the CLI recently shipped and the roadmap includes a VS Code extension and cloud-synced vaults.