Upstream software project

krb5-wallet

Kerberos-authenticated secure data management client

About krb5-wallet

Kerberos-authenticated secure data management client

This project links 3 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

Debian 13 (Trixie): 3 package records. Catalog coverage diagram, not an application screenshot.krb5-wallet: recorded package coverageDebian 13 (Trixie)3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
krb5-wallet
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13
License expression
Not reported
Source repository
Not reported

Source-reported description

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

Kerberos-authenticated secure data management client

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.

Debian 13 (Trixie)

  1. Package krb5-keytab-backend

    trixie (Debian 13 (Trixie)) (net): Provide existing MIT Kerberos keytabs via remctl

    1.7: all

    Source: krb5-wallet

  2. Package krb5-wallet-client

    trixie (Debian 13 (Trixie)) (net): Kerberos-authenticated secure data management client

    1.7: amd64 arm64

    Source: krb5-wallet

  3. Package krb5-wallet-server

    trixie (Debian 13 (Trixie)) (net): Kerberos-authenticated secure data management server

    1.7: all

    Source: krb5-wallet

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.