Result for 00C203489FCC6A156D9F648B5237B41AE9065DC9

Query result

Key Value
FileName./usr/lib/librekallqt.so.246
FileSize4351616
MD5DBB5D3C749C6298752C36E77FA27DCF8
SHA-100C203489FCC6A156D9F648B5237B41AE9065DC9
SHA-25643B826CF054366A7D304699413A028BD73E51D7C08C09245426D8D985662D7EE
SSDEEP49152:v8dMXoPsSrxxqnxuT7LW27uPh2ZOazRyDPd6OM6Lq/90S+2h4S7:QmHS7qnkT7Lx7u52ZOeYAt6nghv7
TLSHT186164959F530CFA8CCB619BB2F3FC35BC710A5B06D27449F8889B17A7CA31854C166A9
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
MD55A3F9EF32F58C96E6B15821A65D3A616
PackageArchs390
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
PackageRelease22.fc19
PackageVersion2.4.6
SHA-1101128603300CC4EB0F6F5C9343A2EA7105BF51F
SHA-256947E0F8ADB2206F322E20C5F7C9674A41EC994E39F4CFAF2E061ACC7C6D67797