Result for 60E9F3E22CC98ED4F016E453CA7EC92C110C2E21

Query result

Key Value
FileName./usr/sbin/twprint
FileSize895784
MD52F330F49A674993FDD233C8E8832ECDC
SHA-160E9F3E22CC98ED4F016E453CA7EC92C110C2E21
SHA-25615D2A2FBCDA76CF79E154FF28EBEF825DA8C7D4F5A52D4B1AC5BD7FBEBD0B6CA
SSDEEP12288:YvMZ0Wl0leQX/4MBBmSY8JsF6hU3YCGP:Y0E0QX/4MBBxY8JWdGP
TLSHT1E7152A0973F98821C6C4E5365679C7E7758AD98269520F1E4FB19AFF2F2B208460DCEC
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5994583480F72B55039BFF1FEE0A10AE0
PackageArchsparc64
PackageDescriptionTripwire 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.
PackageMaintainerFedora Project
PackageNametripwire
PackageRelease11.fc12
PackageVersion2.4.1.2
SHA-16D134D6A355390D209FD75AB58B0B37FD89536D7
SHA-256457E8D79AF1653B364F9B972DB34907017F8E573C5271112FD9FC090507B3FE5