| Key | Value |
|---|---|
| FileName | ./usr/lib/libqca.so.2.0.2 |
| FileSize | 7359384 |
| MD5 | 512D9E67BE02A3BCA556339C3317A9D8 |
| SHA-1 | 77D2EFDC4B2380C04A445C1DA7D50447884B4D44 |
| SHA-256 | A5B918CA36A2E53FF161827756DAF5F3119E8AC9ABCCDA345BB550E9D67C8430 |
| SSDEEP | 49152:qUqSgpTAkwkVgwpDWkHlkzYjVlN8Jbb4IViJ9gZSl7721TJ3Zh1bXqZT63nhzw4B:oWkHlnVlDY3mNSE3KSlRSB |
| TLSH | T182766B56FB598F06C596AE384CFA5737435CDD0212264F6B919A2338BD03AB59F0B30E |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
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 |
|---|---|
| MD5 | A51E7CE13E5AC8761CCE7F5C08E41C81 |
| PackageArch | mips64el |
| PackageDescription | Taking 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! |
| PackageName | qca2 |
| PackageRelease | 2.fc13 |
| PackageVersion | 2.0.2 |
| SHA-1 | 837A6486947D25A369AD73E157C1A6FB740B82BC |
| SHA-256 | 7CB2B3DA959E283DDE319C7249AEB222F955055069F7E5C574890450FBCFBCA0 |