macOS
brew install tnftpprovider-native install command
brew / Rang 2643
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für tnftp in AI-Agent-Workflows.
Installation
brew install tnftpprovider-native install command
Überblick
NetBSD's FTP client
Verlauf
tnftp is the portable packaging of NetBSD's enhanced `ftp` client. It carries the classic Berkeley FTP client lineage forward through NetBSD, while adding script-friendly URL fetching and portability outside NetBSD.
The NetBSD manual page shows both lineages: Berkeley Regents copyrights from the 1980s and early 1990s, and NetBSD Foundation work beginning in 1996 contributed by Luke Mewburn. The NetBSD source version header identifies the product as `NetBSD-ftp` and records a 20260208 version in current source.
The portable distribution history is documented in NetBSD's tnftp archive. The directory message states that tnftp is a port of the enhanced NetBSD ftp client to other systems and that `lukemftp` was renamed to `tnftp`. Archived tarballs show `lukemftp` releases beginning in 1999, a `tnftp-2.0-beta1` tarball in 2003, date-stamped tnftp tarballs through the 2000s and 2010s, and a 2026 tarball.
tnftp's adoption comes from being a maintained, portable BSD ftp client at a time when base-system ftp clients were disappearing, diverging, or lacking HTTP/URL conveniences. The supplied package facts show it in Homebrew, Fedora/DNF, MacPorts, Arch, openSUSE/Zypper, and as `ftp` in Debian and Ubuntu.
The man page's auto-fetching support is a key adoption detail: it can fetch FTP, HTTP, HTTPS, and file URLs directly into the current directory, which made it useful in scripts and package recipes that wanted a familiar `ftp` command with URL support.
Users invoke `ftp` or `tnftp` interactively to transfer files to and from FTP servers, or non-interactively to fetch URLs. The manual page documents `.netrc` support through `-N`, anonymous mode, passive/active behavior, IPv4/IPv6 selection, retries, output naming, custom HTTP headers, and URL auto-fetching.
In package-manager culture, tnftp often appears as a pragmatic replacement for a missing or weaker system ftp client. It gives bootstrap scripts and port recipes a small BSD-licensed network fetcher with predictable behavior across Unix-like systems.
For package nerds, tnftp matters because it is both historical userland and packaging glue. It preserves the Berkeley/NetBSD ftp interface while making that interface portable and useful for scripted downloads, including HTTP(S) URLs.
It also illustrates why package managers sometimes carry tools that look obsolete by protocol name: even after FTP's decline, a compact, scriptable `ftp` command remained useful for compatibility, bootstrap, and reproducible build environments.
Sicherheitslage
broad file, network, media, or database tool signal.
blue Risiko · mittel Konfidenz · tool
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Credential-bearing paths to review before unattended agent runs.
~/.netrcExecutables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
tnftp | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Installationsmetadaten
| Paketschlüssel | brew:tnftp |
|---|---|
| Version | 20260211 |
| Paketmanager | Homebrew |
| Homepage | https://cdn.netbsd.org/pub/NetBSD/misc/tnftp/ |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Quellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.