Result for 042A2F91898ACAFB8F4EDB0B0A58ED651B11E18B

Query result

Key Value
FileName./usr/lib/librekallqt_el32.so.246
FileSize108588
MD57CF034C09A0AE6126793F8F0DEF0CD1F
SHA-1042A2F91898ACAFB8F4EDB0B0A58ED651B11E18B
SHA-2567A2C57ACB15FD1F6502D0FA81311F94DCF8C8877E3B067A56246991AB039940A
SSDEEP1536:f/KpAWUuAQ+wea2oWoYvSnKsPphQxWNRkavo+zyAiK3+iYWFCCPdbC5V:nKpAWUDjzsPp46voxLK3FCCVbCv
TLSHT1F4B30A2373E24513C9405B348A7A4793734EDF80AC84864F6E49AFEE5FB75C11CA6AE1
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
MD5DACB4DAB23628CD7B4CAF9E41D2426E3
PackageArchsparcv9
PackageDescriptionRekall is a database front-end, however, Rekall is not itself a database, and does not include a database. By this we mean that data is stored somewhere else in an SQL server, and Rekall is fundementally just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting...). It is database agnostic, and does not have any preferred database (plugins are available for MySQL and PostgreSQL).
PackageMaintainerFedora Project
PackageNamerekall
PackageRelease5.fc9
PackageVersion2.4.6
SHA-16C93FBC4FAED79C4504E4F0C679F040A9CC4EEFE
SHA-256C51796A7FC69D6528F840F5784E303C00D64C7D69C0D935FE78E79A23FF1CA7F