Result for 7CF98D292E032F96A568F805BA2808BDCC0CD98C

Query result

Key Value
FileName./usr/bin/indextool
FileSize1940352
MD5871830A18EFC3B7490802F19F6BFD151
SHA-17CF98D292E032F96A568F805BA2808BDCC0CD98C
SHA-256F92F3A41E266FDC4CA3DB54281AF01511948675552763E5DA0407AF2D3F1764D
SSDEEP49152:VlI6gZR+UBrx/hAIm3zkPEj8azicfInxjD:VlJ0R+U1x/iImwEjBicfInx/
TLSHT196954B41EE0C4547F0B85BF02A3F52D8F70B7E5651FE46886306AACB672257111EBBB8
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
MD53F3ECC50AC7FDD0205F54919BB4A79F1
PackageArchppc
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-151E5C3B8B32CC860DEB1BE3E9DC6BA97D56142E9
SHA-256845796410E908B5AB20EE4D6C265AFC2C52E96AFF84EDBEED012A6564EB4087E