Ghost FTP 0.99.69 Preview — stronger source-integrity checks
Publication: Source candidate until the canonical v0.99.69 release actually appears with verified native assets. Previous published version: v0.99.68 (15 November 2026).
Safer staged FTP, FTPS and SFTP uploads
- FTP/SFTP upload source snapshots now include an additional bounded SHA-256 digest, checked on the same source pathname and file identity before each transfer attempt and before promotion.
- Small files (up to 64 KiB) are hashed in full. For larger files, the digest covers distinct 64 KiB windows at the beginning, middle and end; additional local I/O remains bounded even for files larger than 4 GiB.
- The new guard detects common same-length source modifications where the modification timestamp was restored and previously matched the metadata-only snapshot, preventing promotion in that detected case.
- Source-window verification also guards automatic retries without silently treating a newly edited file as the original transfer source.
Automated regression coverage
- Same-sized content rewrite followed by restoration of the original modification time.
- Sparse 4 GiB + 16 bytes Linux source: 64-bit length metadata, bounded sample verification, modification at end of source and rejection before promotion. The sparse test does not send 4 GiB over the network or claim to validate real-server throughput.
- Existing protocol E2E, concurrency, transfer ledger, Windows filesystem, UI, versioning, privacy, audit, signing and native packaging gates remain required.
Important security and acceptance limitations
Sampled hashing is not a complete file checksum. Mutations outside the sampled regions, rapid concurrent writes, malicious timestamp/device metadata manipulation and server-side corruption can remain undetected. The local digest is not compared with remote contents. Always use a full SHA-256 comparison and a controlled server when independently validating transfer integrity. Existing FTP rename-overwrite races, staging leftovers, ambiguous acknowledgments and provider-specific cloud behaviors are still documented limitations.
Not certified: Full 4 GiB+ network transfers at 1/4/8 parallel workers under injected faults, physical Windows/Linux credential-vault reboot and locked-store testing, genuine installed-app user acceptance, publisher identity signing and Stable distribution. No source-level test should be represented as complete production acceptance.
See the scoped security and 64-bit test audit and the independent native acceptance matrix.
Release requirements
Do not reuse or modify published tags/assets. After an exact-head pull request passes Rust fmt, tests, Clippy, dependency checks, frontend, security/dead-code checks, FTP/FTPS/SFTP E2E and Windows/Linux native builds, merge to main. Only the verified main release workflow may publish new Portable EXE, Setup EXE, MSI, Linux packages, QA/source archives and SHA-256 checksums.
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.