Result for 0132A7D3A9C2536A77EAFD6CB5AA621B56F81F0D

Query result

Key Value
FileName./usr/lib64/librekallqt_driver_dbtcp.so.246
FileSize74728
MD55381D9582405B95A8422310EBCCEF9F5
SHA-10132A7D3A9C2536A77EAFD6CB5AA621B56F81F0D
SHA-2563C29228D0381D87930C7C2A3B96C46BD3FDC3ED49321A69F6FA9DF1053A55332
SSDEEP768:xoziW1Z35oqrmKSmbB/7Afn5ssWp9dXAbGGTlpBxVwCTTU:WjHeqKO5kPWGhTlxa
TLSHT1FD73B60B37E0C632E98489318033D71FA2CACD8564E54367E6588EFB6DA16C41E5AFF5
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
MD5D8E7BF8FC883023D0183C94793FC5B59
PackageArchsparc64
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-1FB309B9B95AD8B754198E13DDE2584DB51D4E0C5
SHA-2563CF7D6D1EBBD6B2BCB43BB051E4CD56A1E850027BC344D1FBA11A91833DC662E