Upstream software project

fizz

Development files for fizz

About fizz

Development files for fizz

This project links 2 native package records across 1 recorded operating-system release. 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

fizz repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 2 package records. Catalog coverage diagram, not an application screenshot.fizz: recorded package coverageFedora 432 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
fizz
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43
License expression
BSD-3-Clause
Source repository
Open source repository

Source-reported description

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

Fizz is a TLS 1.3 implementation. Fizz currently supports TLS 1.3 drafts 28, 26 (both wire-compatible with the final specification), and 23. All major handshake modes are supported, including PSK resumption, early data, client authentication, and HelloRetryRequest. The fizz-devel package contains libraries and header files for developing applications that use fizz.

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 fizz

    43 (Fedora 43) (Unspecified): A C++14 implementation of the TLS-1.3 standard

    2025.02.03.00-1.fc43: aarch64 x86_64

    Source: fizz

  2. Package fizz-devel

    43 (Fedora 43) (Unspecified): Development files for fizz

    2025.02.03.00-1.fc43: aarch64 x86_64

    Source: fizz

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.