Result for 1639E9B6F3684221814FF3FD565A2714EFF53F72

Query result

Key Value
FileName./usr/bin/relayserver
FileSize133048
MD57EC4E35D34D9674C25CAD83574D537F1
SHA-11639E9B6F3684221814FF3FD565A2714EFF53F72
SHA-25645A8AC8CB6E42F4DFB29F4320295B7017799D545383DC9ED3851160719FB5E71
SSDEEP1536:gzGDLkz0sXpnfs4lcff2b+Lj9g+MzqAAz424CmtqQVGhFAlQhhA4j4JXDLwiKW6k:lEcq6Omq6irBEDaz7KB3A
TLSHT174D3E762FB2E5DC6F6A33D70259F0791C32A680813567098624EDF0E49F3B963607EC9
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
MD51504479F4F1250C931566FE7A43EDC6F
PackageArchppc
PackageDescriptionLibjingle 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.
PackageMaintainerFedora Project
PackageNamelibjingle
PackageRelease2.fc16
PackageVersion0.6.0
SHA-108A088775BCCF98CC666822A1073ADF9F8A913C4
SHA-256E17E5EAE012DF9DDD8A51CB26255E973C1F71CCAFDAD2CB4FC6575E944DF27CC