Skip to content

Security Overview ​

AeroFTP is designed with security as a foundational requirement. Every layer of the application follows a defense-in-depth model where multiple independent controls protect against any single point of failure.

Architecture at a Glance ​

LayerPurposeDetails
Credential storageProtect secrets at restAES-256-GCM vault, OS keyring, Argon2id KDF, optional TOTP 2FA
EncryptionProtect user files and data in transitAeroVault containers, AeroCrypt and rclone crypt overlays, TLS/SSH, archive encryption
AI tool securityControl AI agent capabilitiesBackend grant system, backend-created AeroFTP approval window, tool classification
Supply chainVerify software authenticitySigstore signing, client-side verification, update helper hardening
PrivacyMinimize data footprintNo product telemetry; local storage, configured external services and key-mode boundaries

Layers use separate keys, algorithms and threat models, but shared processes and unlocked endpoints can create common exposure. A compromise of an unlocked endpoint can affect several layers.

Trust Boundaries ​

The Rust backend is the security authority. The web frontend can request operations but cannot bypass backend enforcement:

  • Credentials: Saved-server tools resolve credentials inside the Rust backend and omit them from model results. Setup forms still handle values entered by the user; this boundary is credential isolation from tools and models, not a claim that the renderer never sees input.
  • AI tools: Mutative operations require a grant issued and validated by the backend. Confirmation uses a backend-created AeroFTP approval window or the in-app panel according to the selected mode; Extreme mode accepts frontend tool requests automatically, but protected mutations retain backend approval. See AI tool security for those boundaries.
  • Updates: The backend verifies Sigstore bundles before allowing any installation. On Linux, the privileged helper re-verifies SHA-256 before executing package managers.
  • Compatibility crypto: rclone crypt decryption happens locally in the backend so encrypted remotes can be inspected without handing passwords to external services.

Where AeroFTP Stands ​

In the landscape of file transfer and cloud management tools, AeroFTP combines protocol breadth (8 transport protocols, including SCP, plus 26 native provider integrations) with security depth typically found only in dedicated encryption tools:

  • OpenSSF Best Practices: the badge recorded for the project. This page does not re-check that score
  • Aikido Security: February and March 2026 snapshots in the audit archive. They are not a current subscription status
  • 300+ findings recorded across the audit archive
  • Accepted Rust advisories are the ignore list in src-tauri/.cargo/audit.toml, checked by cargo audit in CI. See Continuous Audit. This line is not a count of open CVEs

Reporting Vulnerabilities ​

Report security issues via GitHub Security Advisories. We respond within 48 hours. See the full disclosure policy and bug bounty program.

aeroftp.app - Released under the GPL-3.0 License. AeroFTP Reviews