Result for 0A4427B63A7E9B48A2A113D77693B38AB9DD414D

Query result

Key Value
FileName./usr/bin/notary-signer
FileSize17494048
MD58785D4FAD90DCEDE954ED4503EAF2EB6
SHA-10A4427B63A7E9B48A2A113D77693B38AB9DD414D
SHA-256B12CCB805769EF41BC884E7C0F6620DB95294B3FD81807FDA83D8459E48D67F9
SSDEEP393216:Xe6kkMo5rQAg9PCPtoDMQSjWEWsmWH3S5m2b:XsZJJ4Ws1i
TLSHT1BA07175EF80DE4A6EE88663077A543EF313D7945CAA4C2334760E969BAE37C48F13590
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
MD5AF37EF86B052A3F444B814C9B5F4A2CF
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
PackageRelease5.20200204gitf255ae7.fc33
PackageVersion0.6.1
SHA-1D572464196EA1CDAAE7506E419B6B44E94D4DF2B
SHA-2563F7154D4380B4F0175654BF76D37BF565EC3AACFEE9F2D718D573C440BEC126C