⚠️ Deprecated: This project is no longer maintained. Please use useFormseal/decrypt instead.
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
If you find a security vulnerability, please report it privately to allow time for a fix before public disclosure.
Do NOT open a public GitHub issue for security vulnerabilities.
GitHub Security Advisories: Use the "Report a vulnerability" button on this repo's Security tab
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Acknowledgment: Best effort (typically within a few days)
- Assessment: Best effort based on availability
- Fix timeline: Depends on severity and maintainer bandwidth
formseal-inbox stores sensitive data (private key) in your operating system's secure credential storage:
| OS | Storage location |
|---|---|
| Windows | Credential Manager |
| macOS | Keychain |
| Linux | Secret Service API (libsecret) |
- Encrypted at rest: Most operating systems protect stored credentials using OS-level encryption tied to your user account
- Access controlled: Requires your user account to access
- Managed by OS: Leverages built-in security features
If the OS keychain is unavailable, the private key is stored in base64-encoded JSON at:
~/.config/formseal-inbox/secrets.json
This mode should only be used in environments where secure credential storage (keyring) is unavailable.
| Data | Stored As | Location |
|---|---|---|
| Private Key | Encrypted | OS Keychain (preferred) or secrets.json |
| Source path | Plaintext | config.json |
| Destination path | Plaintext | config.json |
- Key visibility:
fsi statusmasks the key location, not the key itself - No telemetry: The tool does not send usage data, analytics, or logs externally
- Local operation: All decryption happens locally on your machine
formseal-inbox is a local CLI tool. It assumes:
- The system is trusted by the user
- The user account is not compromised
- The tool is not exposed to untrusted remote input
It does NOT protect against:
- Malware on the system
- Other local users with access to your files
- Physical access to the machine
- Keep your private key secret — never share it
- Use
fsi disconnectwhen done, especially on shared machines - Store decrypted output securely — it contains plain form data
fsi disconnectThis deletes:
- Private key from OS Keychain
- Configuration file (
config.json)
Decrypted messages are NOT affected.