Result for 2AF09CBBEFCFB25CC65F3F9E843078B668ABF1C3

Query result

Key Value
FileName./usr/bin/indexer
FileSize2117416
MD5ED10C9E6BA503E51A9ABD6923D1092CA
SHA-12AF09CBBEFCFB25CC65F3F9E843078B668ABF1C3
SHA-2560F7936860A2D50ECDC6318CDFBB5B2D0232D7CF470434B5059BA8CFDC420BEED
SSDEEP49152:KLrTZO6BLHMiMOL1w6iDSB34Fbon7ScD0:KLr1BBjKOL1w66u34Fbo7ScD
TLSHT1C5A53B807F492DA7E61417B2B22E78F0F39A7CA2437516027B0D574B6CF2251687FE92
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
MD5BF5A59FFA3C2EE9DDA36F48DBE11883A
PackageArchppc64
PackageDescriptionSphinx is a full-text search engine, distributed under GPL version 2. Commercial licensing (e.g. for embedded use) is also available upon request. Generally, it's a standalone search engine, meant to provide fast, size-efficient and relevant full-text search functions to other applications. Sphinx was specially designed to integrate well with SQL databases and scripting languages. Currently built-in data source drivers support fetching data either via direct connection to MySQL, or PostgreSQL, or from a pipe in a custom XML format. Adding new drivers (e.g. to natively support some other DBMSes) is designed to be as easy as possible. Search API is natively ported to PHP, Python, Perl, Ruby, Java, and also available as a pluggable MySQL storage engine. API is very lightweight so porting it to new language is known to take a few hours. As for the name, Sphinx is an acronym which is officially decoded as SQL Phrase Index. Yes, I know about CMU's Sphinx project.
PackageMaintainerKoji
PackageNamesphinx
PackageRelease2.fc18
PackageVersion2.0.3
SHA-19C2AD512C37664E910CCA428D1E98369618DDF79
SHA-256272CC9DB3821985224CC7BE05630BCCE6EC2991F0BE48C27587B5D9EC0142B7E