Result for 0DB29B54F0B1EF400D02965F145E2FA7B1A1D1C2

Query result

Key Value
FileNameprotobuf.spec
FileSize20387
MD51B0EB68792BC3DC0034BE6FCCCC5D878
SHA-10DB29B54F0B1EF400D02965F145E2FA7B1A1D1C2
SHA-2563FAEF12800CB3B15EECB9547046AFE43CF23B91BC06D73E3DBA9366E2A7CF5A1
SSDEEP384:48U3bcCOxg88BExnQ6zlA8ySW7RJCSBy9kf/lTuob4G8pz94I0lArO7084YfaOon:488bcCKBcC3kf/lTuobGpz94I0Az2Pv4
TLSHT172921A3352C111797AC9E5C2F1B06945FB7DD1F8E35A00B530AEC2851B436A8B7BB2B5
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
MD5D9151183B919C9B3246A40BB4B379F16
PackageArchi586
PackageDescriptionProtocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats. Protocol buffers are a flexible, efficient, automated mechanism for serializing structured data – think XML, but smaller, faster, and simpler. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. You can even update your data structure without breaking deployed programs that are compiled against the "old" format.
PackageMaintainerns80 <ns80>
PackageNameprotobuf
PackageRelease1.1.mga8
PackageVersion3.14.0
SHA-1B4158A27336413692D14CC9EA026219D93946664
SHA-2569877FD1E18D399A2C5C0F740EA01C5A099275249DDB2D54E0374351BCEC27D83