Result for 110C9EF8782A20CD0AEB9F9C0F369ABEC8B721F1

Query result

Key Value
FileName./usr/bin/qcatool2
FileSize277992
MD56D474114385E7BA022D7B3283C5AD68F
SHA-1110C9EF8782A20CD0AEB9F9C0F369ABEC8B721F1
SHA-2560226F4C33AA7E55AC2D814FFD2654FB73460BD85AA212D7BF6B3A258371A23ED
SSDEEP6144:LyrENOzTfb75tEv/cexaS5nUOSwdPCEs6KaP0AJHCUDMMBJnLqVryjOZd0Rj:STfb75tEv/cUaQnUOSwd6EwaP0AJHrM8
TLSHT16D441A7D9B468231EA874C305047A2374D509933F919CE86B7CD5A2ADA7FFC9B20A347
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
MD5A817D53FDCC14B7509F4B7D3B2583BEC
PackageArchi686
PackageDescriptionTaking a hint from the similarly-named Java Cryptography Architecture, QCA aims to provide a straightforward and cross-platform crypto API, using Qt datatypes and conventions. QCA separates the API from the implementation, using plugins known as Providers. The advantage of this model is to allow applications to avoid linking to or explicitly depending on any particular cryptographic library. This allows one to easily change or upgrade crypto implementations without even needing to recompile the application!
PackageMaintainerChristian Metzen <metzench@ccux-linux.de>
PackageNameqca
PackageRelease3
PackageVersion2.0.2
SHA-1A53B55A6A79F5651A41A40F2BED186BCE766D5B7
SHA-2565ABB7004D4ECC49AF6E5DF825AC4EBEAD41F797E125A9761B87C87B0F3EA1127