macOS
brew install libidnprovider-native install command
brew / Rang 382
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für libidn in AI-Agent-Workflows.
Installation
brew install libidnprovider-native install command
Überblick
International domain name library
Verlauf
GNU Libidn is the original GNU implementation of internationalized-domain-name handling for the IDNA2003 era, with Stringprep, Nameprep, Punycode, and related TLD validation APIs.
Libidn started as an implementation of the IETF IDN working group's Stringprep and IDNA work. The GNU manual's history section records version 0.0.0 on 2002-11-05 with Stringprep support, version 0.1.0 on 2003-01-05 with IDNA and Punycode support, and version 0.1.11 on 2003-02-26 with a command-line interface.
The March 2003 IDNA RFCs standardized the ASCII-compatible encoding approach that let applications represent non-ASCII domain labels through ASCII DNS labels beginning with the xn-- prefix. Libidn turned that standards stack into a reusable C library and command-line tool.
The manual records a GNU libc add-on proposal in March 2003 and integration in March 2004. The project page notes Fedora Core 3 included Libidn 0.5.6 in November 2004, and that version 1.0 was released on 2007-07-31 to mark stable status after production use.
Libidn spread through network clients and authentication-related software that needed to accept internationalized names while still speaking ASCII DNS or protocol internals. The GNU project page names GNU SASL and Shishi as users for processing user names and passwords.
After IDNA2008 replaced the IDNA2003 standards, Libidn remained important for compatibility with older software and older protocol behavior, while GNU Libidn2 became the successor implementation for IDNA2008 and TR46.
The idn command converts domain names to and from ASCII Compatible Encoding, and the library exposes Stringprep, Punycode, IDNA, and TLD APIs for applications that need deterministic internationalized-name handling.
Libidn is a standards-history package: it ties DNS, Unicode 3.2-era string preparation, Punycode, application compatibility, and distro policy into one small dependency. Package maintainers often encounter it when deciding whether old software needs IDNA2003 compatibility or can move to libidn2.
Its glibc add-on history also makes it a useful example of how networking behavior can move between optional libraries, libc, and application-level dependencies.
Sicherheitslage
library-like package without higher-risk signals.
grün Risiko · niedrig Konfidenz · appliance
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
idn | 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:libidn |
|---|---|
| Version | 1.44 |
| Paketmanager | Homebrew |
| Homepage | https://www.gnu.org/software/libidn/ |
| 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.