Reporting a vulnerability
Email security@slonview.com. Please don't open a public GitHub issue for security problems.
Include the Slonview version, your operating system, steps to reproduce, and what an attacker could do with it. You'll get a reply within 7 days. Slonview is maintained by one person, so fixes ship as fast as that allows, and you'll be credited in the release notes unless you ask not to be.
In scope
- The Slonview desktop app and its release builds.
- Ways around read-only mode that use ordinary SQL, such as committing a write while a connection shows
READ-ONLY. - Credential handling: passwords leaving the OS credential store, or being written to disk or logs.
- TLS or SSH host-key checks that accept what they should refuse.
Known limits, not vulnerabilities
- Read-only mode is a guard, not a permission system. Functions with effects outside the transaction (for example
pg_advisory_lock,dblinkorpostgres_fdw) can still act. Use a role with onlySELECTfor a hard guarantee. preferandrequireTLS modes encrypt but don't verify the server certificate, as in libpq. Useverify-fullon untrusted networks.