Result for 0E978BFEDFE15DE669B1878C634358D0E3E724E4

Query result

Key Value
FileName./usr/bin/notary-signer
FileSize13244132
MD5E575EEF83A7E200EDF168654A7231B9A
SHA-10E978BFEDFE15DE669B1878C634358D0E3E724E4
SHA-25696334B587C94FAEDF3A5260058AE1993ADA523E3003DCA68F32447CADFAA9895
SSDEEP98304:6ZOY6AyKJHCVFLL4qrdmCU9CGa25Bc4OR2MskCgLkQO8SOKLk/nKhASRQdJCz:06AyKQF9fGaq/OHPLkQFfD8
TLSHT173D61A9FB8A54642C5E42A75B8BE82C833E716BD87C262975E00EE343F7F1DA0935744
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
MD58BBB9F0F33DAA45A678D800DB05B64FC
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
PackageRelease10.20200917git84287fd.fc34
PackageVersion0.6.1
SHA-1536872218503ABA5989F581B2E4B5A03B8820443
SHA-256DCFA952BAFE9C6C49A6C1724D7ABBE43E232A41D03FEA28990311F0402FECCA9