Upstream software project

thc-ipv6

Toolkit for attacking the IPv6 protocol suite

About thc-ipv6

Toolkit for attacking the IPv6 protocol suite

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

thc-ipv6 repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.thc-ipv6: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
thc-ipv6
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
LicenseRef-Callaway-AGPLv3-with-exceptions
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

A complete tool set to attack the inherent protocol weaknesses of IPv6 and ICMPv6, including an easy to use packet factory library.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package thc-ipv6

    43 (Fedora 43) (Unspecified): Toolkit for attacking the IPv6 protocol suite

    3.8-8.fc43: aarch64 x86_64

    Source: thc-ipv6

Fedora 44

  1. Package thc-ipv6

    44 (Fedora 44) (Unspecified): Toolkit for attacking the IPv6 protocol suite

    3.8-9.fc44: aarch64 x86_64

    Source: thc-ipv6

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.