pkg.sopackage field notes

brew / Rang 2643

tnftp mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für tnftp in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install tnftp

provider-native install command

Überblick

Paketzusammenfassung

NetBSD's FTP client

Befehle und Aliase

  • tnftp

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 1985-1994: Berkeley FTP client ancestry appears in the NetBSD manual page copyrights and SCCS marker.
  • 1996: NetBSD Foundation ftp work begins in the manual page copyright range.
  • 1999: `lukemftp-1.0.tar.gz` appears in the NetBSD tnftp archive.
  • 2003: `tnftp-2.0-beta1.tar.gz` appears after the rename from lukemftp to tnftp.
  • 2023: NetBSD archive publishes date-stamped tnftp tarballs for April and May 2023.
  • 2026: NetBSD current source identifies `FTP_VERSION` as `20260208`, and the archive contains `tnftp-20260211.tar.gz`.

Related projects

  • Related to NetBSD's base-system `ftp` client in `usr.bin/ftp`.
  • Closely paired in the portable archive with tnftpd, the corresponding NetBSD FTP server port.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:ftp,client

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

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 files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.netrc

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
tnftpExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und 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.

Seite generiert2026-08-03
Manager-Version20260211
Manager aktualisiert
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:tnftp
Version20260211
PaketmanagerHomebrew
Homepagehttps://cdn.netbsd.org/pub/NetBSD/misc/tnftp/
Bottlenicht erfasst
Dienstkeiner deklariert

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation