Result for 253E37053EECA579B7896961D1D0A61F1770DA33

Query result

Key Value
FileName./usr/sbin/twprint
FileSize1151288
MD58AE89B0D60155D607310BF433504C071
SHA-1253E37053EECA579B7896961D1D0A61F1770DA33
SHA-2566277A60140C16335DA9DBC8C783CCD7890B61B9E0EBBC94ACEE54001ED306048
SSDEEP12288:fO6dFZ3oWwWN2Zib4dugMbxLjYZ5rAOkvliLK8sJTytN9R4FH+lG0xqGaIFzx0MA:fjDjw8tcnr058bFaW
TLSHT12335A7A6B030D18EC4227B33B9419FF2A13638B453EA751893FEEF654CF97014559A3A
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
MD565DC3208856CFDBAD085608B8713712A
PackageArchs390x
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
PackageRelease9.fc11
PackageVersion2.4.1.2
SHA-136C1577CEB8BCFF0A79CCAC49A26F9C848F31D17
SHA-2568B5DE57A6249B00AE2B26548F520F7C8FF1CE1583E81CBC02DE3BB7D06A23BED