Packages / openSUSE Tumbleweed / Productivity/Networking/DNS/Utilities / libidn-tools

Package: libidn-tools (1.44-1.3)

Command line utility to convert Int. Domain Names

GNU Libidn is an implementation of the Stringprep, Punycode, and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group. It is used to prepare internationalized strings (such as domain name labels, usernames, and passwords) in order to increase the likelihood that string input and string comparison work in ways that make sense for typical users around the world. The library contains a generic Stringprep implementation that does Unicode 3.2 NFKC normalization, mapping and prohibition of characters, and bidirectional character handling. Profiles for iSCSI, Kerberos 5, Nameprep, SASL, and XMPP are included. Punycode and ASCII Compatible Encoding (ACE) via IDNA is supported.

Package information

Homepage
[https://www.gnu.org/software/libidn/]
License
(GPL-2.0-or-later OR LGPL-3.0-or-later) AND GPL-3.0-or-later
Downstream package maintainer
Unknown: not reported in the indexed source
Source package
[libidn]
Software project
[libidn2]

Versions and downloads for libidn-tools

Version / releaseArchitecture / repositoryPackage sizeInstalled sizeFilesPublisher repository artifact
1.44-1.3tumbleweed / ossx86_64openSUSE Tumbleweed · OSS · multi-architecture189 KiB483 KiBlist of fileslibidn-tools-1.44-1.3.x86_64.rpm
About these downloads

Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.

Other packages built from libidn

Dependencies and recommendations for libidn-tools

  • dep: libidn.so.12()(64bit)

    Package not available

  • dep: libidn.so.12(LIBIDN_1.0)(64bit)

    Package not available

  • dep: libc.so.6(GLIBC_2.34)(64bit)

    Package not available

Package file paths (43)

Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.

  • /usr/bin/idn
  • /usr/share/doc/packages/libidn-tools
  • /usr/share/doc/packages/libidn-tools/AUTHORS
  • /usr/share/doc/packages/libidn-tools/ChangeLog
  • /usr/share/doc/packages/libidn-tools/FAQ
  • /usr/share/doc/packages/libidn-tools/NEWS
  • /usr/share/doc/packages/libidn-tools/README
  • /usr/share/doc/packages/libidn-tools/THANKS
  • /usr/share/emacs
  • /usr/share/emacs/site-lisp
  • /usr/share/emacs/site-lisp/idna.el
  • /usr/share/emacs/site-lisp/punycode.el
  • /usr/share/info/libidn-components.png
  • /usr/share/info/libidn.info.gz
  • /usr/share/licenses/libidn-tools
  • /usr/share/licenses/libidn-tools/COPYING
  • /usr/share/licenses/libidn-tools/COPYING.LESSERv2
  • /usr/share/licenses/libidn-tools/COPYING.LESSERv3
  • /usr/share/licenses/libidn-tools/COPYINGv2
  • /usr/share/locale/cs/LC_MESSAGES/libidn.mo
  • /usr/share/locale/da/LC_MESSAGES/libidn.mo
  • /usr/share/locale/de/LC_MESSAGES/libidn.mo
  • /usr/share/locale/eo/LC_MESSAGES/libidn.mo
  • /usr/share/locale/es/LC_MESSAGES/libidn.mo
  • /usr/share/locale/fi/LC_MESSAGES/libidn.mo
  • /usr/share/locale/fr/LC_MESSAGES/libidn.mo
  • /usr/share/locale/hr/LC_MESSAGES/libidn.mo
  • /usr/share/locale/hu/LC_MESSAGES/libidn.mo
  • /usr/share/locale/id/LC_MESSAGES/libidn.mo
  • /usr/share/locale/it/LC_MESSAGES/libidn.mo
  • /usr/share/locale/ja/LC_MESSAGES/libidn.mo
  • /usr/share/locale/ka/LC_MESSAGES/libidn.mo
  • /usr/share/locale/ko/LC_MESSAGES/libidn.mo
  • /usr/share/locale/nl/LC_MESSAGES/libidn.mo
  • /usr/share/locale/pl/LC_MESSAGES/libidn.mo
  • /usr/share/locale/pt_BR/LC_MESSAGES/libidn.mo
  • /usr/share/locale/ro/LC_MESSAGES/libidn.mo
  • /usr/share/locale/sr/LC_MESSAGES/libidn.mo
  • /usr/share/locale/sv/LC_MESSAGES/libidn.mo
  • /usr/share/locale/uk/LC_MESSAGES/libidn.mo
  • /usr/share/locale/vi/LC_MESSAGES/libidn.mo
  • /usr/share/locale/zh_CN/LC_MESSAGES/libidn.mo
  • /usr/share/man/man1/idn.1.gz

Field source: openSUSE Tumbleweed OSS

Known vulnerabilities

CVESeverityVersion impact
[CVE-2026-57053]

Published:

GNU libidn before 1.44 is prone to out-of-bounds reads of uninitialized memory in the ToUnicode APIs because of mishandling in idna_to_unicode_internal. The affected code is not present in libidn2.

Medium(4)Unknown
Details (1)
  • 1.44-1.3 · x86_64 · tumbleweed

    Unknown · Fixed: 1.43-160000.3.1

    Version impact unknown

    pypi · libidn · opensuse · leap 16.0

Last synced:

[CVE catalog]

Checksums

Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.

1.44-1.3 / x86_64Observed Sep 1, 2026sha512 11cea3a74178…d3cf6bf1Source-reported digest

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Source-reported digest (sha512): 11cea3a7417841127da51503a9fa9762496b485530c2b6939adce62b79971095e1e9f92ade885a68a3fb8dc4436b6865bee3a751587ad8a076de1cb1d3cf6bf1

Field source: openSUSE Tumbleweed OSS

Sources

  • Authoritative source; repository metadata signature verified

    Signature evidence

    tumbleweed-oss-multiarch:4db10cdde3ad82c7e22be35753c9e164b4bdd30f92db4aee17a0d4c94c5f902f

    Repository-signature verification record
    Signed-object SHA-256
    4db10cdde3ad82c7e22be35753c9e164b4bdd30f92db4aee17a0d4c94c5f902f
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable

Use this package

OpenFactory can boot this operating system in a browser VM, or start a build that includes the native package name from this record.