Result for 270E13F9AC0317118BA11091DDBB19525E2BCEAA

Query result

Key Value
FileName./usr/sbin/siggen
FileSize971768
MD5CD612BC89D7EE972F45608DFD514544D
SHA-1270E13F9AC0317118BA11091DDBB19525E2BCEAA
SHA-256DD9AE98F51F9969CCDFA56196EBA8A29E80593D7EAAC4A0D0FE3235395087F47
SSDEEP12288:4A8okmu+ij9HNyr+psM4rbfiKvSLUpD2FS4uwYFAPnYh:4A8okHptyr+psvfvxpDIS4uwc
TLSHT1E8255C8CF68C3852E29BF27CFE8CD7F96427B962D3190096342712A89BD9D958F77005
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
MD50B583B1618DB4DAB90616B624F78363B
PackageArchaarch64
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
PackageRelease1.el7
PackageVersion2.4.3.7
SHA-145D52A990C9277F2CA404459F336990DBF279D77
SHA-256C38C7E13125899103110E2BE345C75607774A09EC389869CA0AA33B82DF1B095