Result for 36D02A6A5DA0AA6F4D7255B8AD838442E2E65AF2

Query result

Key Value
FileNametripwire.spec
FileSize17298
MD52E2D87213916BF8DBC36382D6003CE1F
SHA-136D02A6A5DA0AA6F4D7255B8AD838442E2E65AF2
SHA-25695B759B1975524F02D041BD759E8C3F88D584D751EB7197C64171D43A2847D12
SSDEEP384:j4n1EuFgmDFbF0gUFRFDoi/e/f3rb/5/9/btaJr6w4kNrdNnNCNXNHNyhoxvphhm:6yuF/b3i+U
TLSHT1D172E976634D293337C22F95D694390AF67D88BCEF76B05C505A924C318B8B8B27A11F
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
MD5179177D96BE48571BC816498C68736CC
PackageArcharmv7hl
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
PackageRelease7.fc33
PackageVersion2.4.3.7
SHA-181B0B2ACAFF4076A13E1CE2DE8891AC80C1D4583
SHA-2568DB0F12E09FF07E4AD53DD09E081A69CC1F855DD53F525E14112DBDCD2EAF284