Result for 126F1B806112118BDDF3812BB71DE6031E355A2F

Query result

Key Value
FileName./usr/sbin/siggen
FileSize1240368
MD5EBC343FC78CF51C376DEFB8C8CFD146D
SHA-1126F1B806112118BDDF3812BB71DE6031E355A2F
SHA-2563797CA4535733CD178EE30353FEA108947B16F53137469B8A8272D47B6765F6D
SSDEEP12288:FuYsiTpWEHJaRLqizntCuP2s/zQrkhrASkewOcXCSG4vVhjeh9ol/x0aD6py9g:kMTe/syre7VRe9Mee
TLSHT15C45E7C17F485C6FE3482572512A1EF0E7667CD262B47E203B0E2B9B5D97B04283EDA5
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
MD521A5B1065591EE510F73012009274230
PackageArchppc64
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
PackageRelease4.fc20
PackageVersion2.4.2.2
SHA-150AFA281DEF70D3E2BFC3EFE4A0BE599F6CD5D7E
SHA-25615768F4CFE1D7C199D368FA7A5CAAB76F5218D831CF2B49223D0E7B529DC25BA