Result for 2A75BBACD36B28F2C93C4A021499B6D34626B462

Query result

Key Value
FileName./usr/bin/notary
FileSize15721016
MD5A3AA1D4C5C3F6617F0D9EB18A2E2437D
SHA-12A75BBACD36B28F2C93C4A021499B6D34626B462
SHA-256AB1ACED44E6940BAFA4C2EC0F28FF4BA302C423FB5C5915E6CD7BA8FBEB6EB88
SSDEEP98304:XiZRZaG1ikASidKSZmrscydLHzsIN5ya3gQvuqxmNCiKcti4Fx7nvaAwB:RkASidpZmrOdLHzPNrQQv3W7tNz
TLSHT1AEF63A46FC8240EDC1BEE1708AD56332B9713899C77437870FA09A593A95BB46B7E3D0
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
MD5DA7404B68CA6F669389B26CBE3EF9E72
PackageArchx86_64
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-1F9EE204DCFED14BE61D94C3700545136C255C8F5
SHA-256220C1C2E86EBD58E20919C281AD35F2DFB64FB27A6256C8E02A6E60232E8CDDF