SECURITY

High-risk actions need clear boundaries and confirmation.

Kelorvi does not bypass server permissions or hide host-identity changes. This page describes the current Windows Beta.

Connection trust

The first connection shows a fingerprint. A change to a trusted fingerprint blocks the connection instead of silently accepting it.

Use passwords, private keys, or system OpenSSH Agent. Agent keys remain under operating-system control and are never read or stored by Kelorvi.

Only resolvable alias chains are imported, with a hop limit. Cycles, conflicts, and unsupported ProxyCommand values never run silently.

Passwords, private-key contents, key passphrases, and Agent keys never enter SQLite exports.

Directory transfers use task-specific temporary locations and commit only when every file is complete.

Listeners bind to loopback by default. 0.0.0.0 requires explicit confirmation, and an SSH disconnect closes the listener.

Permission failures provide context and copyable suggestions, but Kelorvi never runs sudo, chmod, or chown automatically.

01
Avoid production harm
Do not test against third-party or production systems, and do not access more data than needed to demonstrate the issue.
02
Minimize evidence
Record version, impact, steps, and sanitized logs. Never send real secrets or full production configuration.
03
Use the controlled channel
Private-beta testers should reply to their invitation and mark it Security. A public security contact will be published before public release.