Upstream software project

tripwire

A tool to observe the filesystem

About tripwire

A tool to observe the filesystem

This project links 7 native package records across 7 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

tripwire repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.tripwire: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
tripwire
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Source repository
Open source repository

Source-reported description

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

Tripwire is a very valuable security tool for Linux systems, if it is installed to a clean system. Tripwire should be installed right after the OS installation, and before you have connected your system to a network (i.e., before any possibility exists that someone could alter files on your system). When Tripwire is initially set up, it creates a database that records certain file information. Then when it is run, it compares a designated set of files and directories to the information stored in the database. Added or deleted files are flagged and reported, as are any files that have changed from their previously recorded state in the database. When Tripwire is run against system files on a regular basis, any file changes will be spotted when Tripwire is run. Tripwire will report the changes, which will give system administrators a clue that they need to enact damage control measures immediately if certain files have been altered.

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 12 (Bookworm)

  1. Package tripwire

    bookworm (Debian 12 (Bookworm)) (utils): file and directory integrity checker

    2.4.3.7-4+b15: amd64 arm64

    Source: tripwire

Debian 13 (Trixie)

  1. Package tripwire

    trixie (Debian 13 (Trixie)) (utils): file and directory integrity checker

    2.4.3.7-6+b17: amd64 arm64

    Source: tripwire

Fedora 43

  1. Package tripwire

    43 (Fedora 43) (Unspecified): IDS (Intrusion Detection System)

    2.4.3.7-20.fc43: aarch64 x86_64

    Source: tripwire

Fedora 44

  1. Package tripwire

    44 (Fedora 44) (Unspecified): IDS (Intrusion Detection System)

    2.4.3.7-21.fc44: aarch64 x86_64

    Source: tripwire

openSUSE Leap 15.6

  1. Package tripwire

    leap-15.6 (openSUSE Leap 15.6) (Productivity/Security): A tool to observe the filesystem

    2.4.3.7-bp156.3.6: aarch64 ppc64le s390x x86_64

    Source: tripwire

openSUSE Leap 16.0

  1. Package tripwire

    leap-16.0 (openSUSE Leap 16.0) (Productivity/Security): A tool to observe the filesystem

    2.4.3.7-bp160.1.12: aarch64 ppc64le s390x x86_64

    Source: tripwire

openSUSE Tumbleweed

  1. Package tripwire

    tumbleweed (openSUSE Tumbleweed) (Productivity/Security): A tool to observe the filesystem

    2.4.3.7-2.7: x86_64

    Source: tripwire

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.