| Key | Value |
|---|---|
| FileName | ./usr/lib64/libjinglebase.so.1.0.0 |
| FileSize | 1219216 |
| MD5 | 6BD36136FE57998666E9162656C721BD |
| SHA-1 | 58BB90DF3987B0CAAD57A46BD542D518D350673A |
| SHA-256 | 635E2658187D9CF7DA6E3049CC9A3AA89565825903B908D6A1B7F25F03B16681 |
| SSDEEP | 12288:ky1HgHGV00aoWDKU/efi575hXaQsIGjBiZFYzXKhUKxLXVv+:Hu7LtGjByFWJ+ |
| TLSH | T181450AC6BACD5CD3D31EABB0464E2FB4D79C5D1429AE30643B8D9F6906D239C740AE90 |
| 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 | 82BBF18E102EB456D26192654534B7F8 |
| PackageArch | ppc64 |
| PackageDescription | Libjingle is Google Talk's implementation of Jingle and Jingle-Audio (proposed extensions to XMPP) to interoperate with Google Talk's peer-to-peer and voice calling capabilities. In addition, it is a P2P (peer-to-peer) and RTC (real-time communication) stack that builds on XMPP. If you don't need any P2P or RTC, you can use any XMPP stack. If you do, then you might want to use libjingle. In fact, you can even use libjingle on top of another XMPP stack. |
| PackageMaintainer | Koji |
| PackageName | libjingle |
| PackageRelease | 2.fc16 |
| PackageVersion | 0.6.0 |
| SHA-1 | 35209025405B19F22CFBCE01F7503CDFC6A33AA0 |
| SHA-256 | 43DDC7BAB33710FD27991FFB4E69B5CB74AA1CE9193B898818E700C06D8E8A18 |