Repository navigation
Ghost FTP 0.99.71
Pre-releaseGhost FTP 0.99.71 Preview — Windows shell and terminal hardening
Status: Source candidate until the GitHub release workflow actually publishes this version. Previous public release: v0.99.70 Preview, 18 November 2026.
Windows stability, security and responsiveness
- Replace unqualified
rundll32.exelaunch in the approved external URL command and the edit-in-place file association with the WindowsShellExecuteWAPI. This prevents Ghost FTP itself from resolving a helper executable through a potentially attacker-controlled current directory or PATH. - Initialize an appropriate COM apartment for the native Shell operation, release it after completion, and run external browser launch on a dedicated blocking worker to avoid unnecessary Tauri GUI stalls.
- Reject oversized or malformed
ghostftp://protocol-handler URLs before expensive decoding. Bound the total URL to 16 KiB and query parameters to 64, and reject control-character injection, userinfo, URL ports and fragments. - Decode SSH terminal text across packet boundaries with bounded (at most three incomplete bytes) UTF-8 carry state for stdout and stderr separately; avoid event-loop bias that can starve output under sustained input.
- Add Rust regression tests and negative full-security-audit tests for each critical protection.
Audits and validation
- Whole-repository conservative dead-code and security static audit remains mandatory. A static or reference-count candidate is NOT proof of safe removal.
npm run check:dead, TypeScript checks, Go tests/vet, Rust fmt/tests/Clippy, Tauri native builds and genuine FTP/FTPS/SFTP protocol E2E remain mandatory on exact PR SHA. - Windows Shell/COM opening, native file associations, first-frame GUI, credential-vault persistence, real 4+ GiB transfer fault injection and performance benchmarking require independent native acceptance.
- Clean up two unreferenced retired v8 pixel-concept tools from
tools/qa; historical reference documentation and active genuine capture validation stay intact. Refer to Windows audit and manual test matrix.
Release policy
Do not merge or publish before all mandatory exact-head checks pass. Windows Portable EXE, Setup EXE, MSI and Linux AppImage, DEB, RPM plus source/QA archives must be validated as nonempty artifacts with SHA-256 checksums. Stable/signing certification is not claimed. Published versions and their assets are immutable.
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.