Result for 2D3C65A2DA4FFB64E483A1A91E59AB19B54E8B32

Query result

Key Value
FileName./usr/bin/notary
FileSize12189316
MD570255A4F3FB6A9E7716F1DC57D3973FF
SHA-12D3C65A2DA4FFB64E483A1A91E59AB19B54E8B32
SHA-25647C000A1108DB69C1F08A3C2BC9665164BE44A53CB20E05F506E9976B274466C
SSDEEP98304:MCTeW6LChN6Vr1skvhpUGEYDDxPQ4OPr4YFJ/jpnPaAw:9q5WcWGnVBY9vL
TLSHT1C4C65A5BB8655682C5E02A35F8BD82C833A312BD8BD316965E06DE347F7F1DA0E36704
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
MD56DBAF4E3D8B63D28A34422A30B9DAA43
PackageArcharmv7hl
PackageDescription The Notary project comprises a server and a client for running and interacting with trusted collections. See the service architecture documentation for more information. Notary aims to make the internet more secure by making it easy for people to publish and verify content. We often rely on TLS to secure our communications with a web server, which is inherently flawed, as any compromise of the server enables malicious content to be substituted for the legitimate content. With Notary, publishers can sign their content offline using keys kept highly secure. Once the publisher is ready to make the content available, they can push their signed trusted collection to a Notary Server. Consumers, having acquired the publisher's public key through a secure channel, can then communicate with any Notary server or (insecure) mirror, relying only on the publisher's key to determine the validity and integrity of the received content.
PackageMaintainerFedora Project
PackageNamegolang-github-theupdateframework-notary
PackageRelease4.20200204gitf255ae7.fc32
PackageVersion0.6.1
SHA-11F36FE6769B4A07E222B077ADDC75D6F9097490F
SHA-2561DAED8A5116B6BBCAF4A1CD4FC0B83F723F0765F8A0DEFD99D0A2563352949A2