Result for 0508A10A4A74E6AEC3445FFEA95A404DB99E1C44

Query result

Key Value
FileName./usr/bin/notary-signer
FileSize13997340
MD5FCF092B73F57C98D1473389162519079
SHA-10508A10A4A74E6AEC3445FFEA95A404DB99E1C44
SHA-256BA1253A1897F9A488E4B89B937D97E74771E82B23E3D1AF6202908E2AC9880D4
SSDEEP98304:AvpIFZvGZ43wWnL+nvtwBz58KOTCZFxL8oQ4aRKj5wu0HsPd9ggAdFpN3FuTnPaO:USFFS4A8bzFxORWwR3gQpNEHv
TLSHT1A4E64A9FF8A68682C5E42A79F8BD82C832E316B987C751575E00DE343BBF5DA0935704
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
MD5CF18BD9FA9B55CC74F33D4F49372A28D
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
PackageRelease5.20200204gitf255ae7.fc33
PackageVersion0.6.1
SHA-1FC2B47A355212530BAD07D15263E8258D32D410B
SHA-25621A3F32655D29CDC035CA1A3FFAF8491DA27FACC37085F57A7AFC5ACCBC5B76B