Ghost FTP by Brendigo
Status: development candidate, not yet published. Date: 22 November 2026.
Previously published: v0.99.76.
Live protocol reliability and fault injection
- Extend loopback FTP and explicit FTPS E2E: establish a disposable profile, stream a binary sentinel, reauthenticate the same session twice, verify original bytes after each reconnect, and ensure explicit Disconnect prevents all later operations and reconnection on that session ID.
- Open the same profile in a new authenticated session after Disconnect and verify that its session ID differs and the original remote bytes survived, before cleaning up the disposable fixture.
- Inject a deterministic source read failure after 96 KiB while uploading 2 MiB + 257 B into a unique staging sibling, reconnect the control channel, verify the existing final target is unchanged, remove the partial staging sibling if present, and assert no staging orphan remains. This is not a simulated physical network drop or process crash.
- Add a real, bounded-memory streamed upload/download SHA-256 matrix for 16 MiB + 17 B on FTP, explicit FTPS, SFTP (Linux), and FTP (Windows). Retain the existing 1/4/8 workers at 1 MiB + 17 B and separately opt-in >4-GiB stress.
Visual acceptance fail-closed comparison
- Add
--require-exacttotools/qa/compare-screen-references.py. A one-channel change of 1 in any pixel now fails strict 1:1 evaluation, even when it remains below the existing visually meaningful change threshold of 12. - Add tests proving exact equality, one-channel difference, missing screenshot and comparison-only reporting; run these on the native Linux build CI with Pillow.
- No 59-screen 1:1 approval claimed: the reference ZIP is illustrative artwork, and genuine Windows/Linux native captures at controlled DPI, locale and interaction states must be compared to user-approved references before recording any pass.
Not yet verified
- Physical network cable/Wi-Fi loss, server power-cycle, large (>4 GiB) network transfers and disk-full recovery on real target machines.
- Windows 10/11 Credential Manager and Linux Secret Service persistence/reconnection across native logout/reboot.
- Authenticated external cloud accounts, OAuth expiry/revocation, provider 429/5xx behavior, quotas and upload session cleanup.
- Independent signed Stable release audit, legal review and 59/59 verified native screenshot parity.
Release gates
Do not publish until exact-head quality, Rust tests/Clippy, real FTP/FTPS/SFTP and Windows FTP protocol E2E, Windows hardening, and Windows/Linux native packages all pass, then repeat on the merged main commit. Only a public, immutable v0.99.77 GitHub Release with complete Windows Portable/Setup/MSI and Linux AppImage/DEB/RPM plus SHA-256 inventory establishes actual publication.
Linux installation: choose the correct Ghost FTP package
Platform: Linux x86_64 / amd64. These are package-family labels, not
certifications that every distribution/version has been tested. The native
Windows/Linux build currently runs on an Ubuntu 22.04 x86_64 GitHub runner;
installed-device checks across other distributions remain required.
| Linux edition in GitHub Releases | Intended distribution / installation family | Important prerequisite |
|---|---|---|
GhostFTP-Linux-amd64-v<VERSION>.deb
| Debian, Ubuntu, Linux Mint, Pop!_OS, and compatible Debian-family amd64 systems | APT/dpkg dependencies, WebKitGTK 4.1 and compatible GTK/GLib; test on the target distro release. |
GhostFTP-Linux-x86_64-v<VERSION>.rpm
| Fedora, openSUSE, RHEL-compatible RPM-based x86_64 systems | RPM runtime dependencies, WebKitGTK and GTK availability differ. Package format alone does not prove the build launches. |
GhostFTP-Linux-x86_64-v<VERSION>.AppImage
| Portable / cross-distribution candidate for many glibc-based x86_64 desktop systems | Check FUSE/AppImage runtime, compatible glibc, WebKitGTK/GTK libraries and display server. Not guaranteed universal. |
GhostFTP-Linux-x86_64-v<VERSION> / .tar.gz
| Manual / advanced installation on compatible x86_64 desktop Linux | Not statically linked; administrators must supply all system runtime dependencies and desktop integration. |
Replace <VERSION> with the exact published tag number. Verify
GhostFTP-v<VERSION>-SHA256SUMS.txt before executing installers. A SHA-256
checksum only verifies integrity against that manifest; it does not prove
publisher identity or replace a cryptographic code signature.
No native package is currently built for Linux ARM64/aarch64,
32-bit x86, musl-only Alpine, or every NixOS/immutable-container configuration.
Arch Linux, Manjaro, EndeavourOS, Gentoo, elementary OS and others may be
candidates for AppImage/manual installation, but are not certified based
solely on an Ubuntu runner. Check compatible dependencies first; do not force a
Debian RPM/DEB package onto an unrelated distribution. On Wayland systems,
GTK/WebKit or XWayland availability can affect behavior.
Required acceptance before claiming distribution support
For each distribution and version named as tested, record its exact image
version, x86_64 architecture, display protocol (X11/Wayland), WebKitGTK/GTK
versions, GNOME Keyring/KWallet state, and the native binary hash. Verify:
- Install, first launch, File Manager/Sites/Transfers/Settings/Sync navigation,
resize at 1290×852 and 480×600, and correct keyboard focus. - FTP warning, verified FTPS TLS and SFTP SSH host-key checks on actual
endpoints; failed identity checks must not connect. - Queue retry/cancel, interrupted upload/download preservation, symlink and
overwrite safety, and shutdown/restart without losing profile metadata. - OS-backed credentials with locked and unavailable Secret Service; no
plaintext fallback or secret-bearing logs. - Uninstall and reinstall without silently deleting stored user documents,
connection profiles, or keys.
Current GitHub Actions Linux QA produces real Xvfb/WebKit screenshots of
seven core workspaces, not mockups. Those captures prove native rendering under
the CI environment; they do not certify a GNOME/KDE/Wayland distro or pixel
parity with all 29 user-supplied Linux design references.
Related: Linux handbook ·
Native desktop build ·
Published releases.
Operational prerequisites for unsigned desktop builds
Running the native binary does not require a purchased signing certificate. Verify the SHA-256 checksum of your package against the matching official release manifest; this validates file integrity, not cryptographic publisher identity. Saved credentials require an unlocked Secret Service provider and the secret-tool client (the DEB declares libsecret-tools, the RPM declares libsecret). An unavailable vault is a blocking error, not a reason to store plaintext passwords. Before upgrading, create an encrypted backup and ensure all transfers are finished. The desktop Updates screen offers the complete GitHub Releases index because signed auto-updates and manually downloadable package editions are independent.