Result for 7BF701FDB567711FBE649C88C110C4ABE4A81CFA

Query result

Key Value
FileName./usr/sbin/tripwire
FileSize1839416
MD5E85004BDC0D34FA50320997C41F464C5
SHA-17BF701FDB567711FBE649C88C110C4ABE4A81CFA
SHA-256C7D8781B3F5447D28C23349C4AECC6AEB87444ECC85C677EDDB7C2AB551F1B64
SSDEEP24576:mawusp3s2+4aUw8v7MuLiaMycDNAcIljROvD52MI2hNi:Iusp3+TUw8TMcialcDNAcIljEbPi
TLSHT13A850AC2BA841D6FE3C49D79701E39B0E77EEC61497EBD286F0E17DB46D2204290E994
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
MD5328A3F272CB424BC7260C74C8C5B9589
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
PackageRelease9.fc23
PackageVersion2.4.2.2
SHA-115A024856EEC6FBDBB123179780A3A2FEFF9939D
SHA-2560BC71DC00D6704DBA8709D96393E2C5A37826D86E5DA89C5ADAFD2991540990B