Result for 266EA66576AD626468EB6940842BB9A09915898B

Query result

Key Value
FileName./usr/bin/notary
FileSize13726048
MD5DFA55E3642A311DC2140BAE73B1B483A
SHA-1266EA66576AD626468EB6940842BB9A09915898B
SHA-256A5D1827517028276A7665664B38D308B7C4790E397007CAFD14919FD3C3D6D2D
SSDEEP196608:kb05wMW7F9y7tdkqP7hSzPaJOquH5QnC78U7uQbd:kb02M2nw4qP7hSzPaJOquZQnCVx
TLSHT172D6F95EF81DE496EEC86730F7A542EB313DB848EA71C1325760AA65F6E37C44E13422
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
MD57C74CE6531ADD0C9F283541FF3CCB77D
PackageArchaarch64
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
PackageRelease10.20200917git84287fd.fc34
PackageVersion0.6.1
SHA-16388509A1C1044A9272A2377F63F79D2C269AA27
SHA-2560C2D6DDBEE92C7FA7F647382DBDAEC10D14AA7FF34B2298A076A9261FE44ABE3