Result for 073947DBA2372674361B169A9A2DC5A13DD635FC

Query result

Key Value
FileName./usr/bin/escrow
FileSize14473712
MD582315EC9609E4F24D26944AE77A05517
SHA-1073947DBA2372674361B169A9A2DC5A13DD635FC
SHA-2561D8D446DD6B86D97686FB9AA1C073B72FFEFC42AAA87E1A3ECCB895126CD48E7
SSDEEP98304:7+osDJni3Ox0jawhaGLj3NWv/fFGUoPM+QxqfSP270DtSmT40YaaHYngmNIpqHFN:aBMWLXh8XiPDx6bg97j
TLSHT1D0E6194DF80DE1D6EE98A63177AA06EF312D784CCAA1C1335B60C974BAF33C95A17161
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
MD54784BA5E3160532C2EF78F129AD9ADB6
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
PackageRelease4.20200204gitf255ae7.fc32
PackageVersion0.6.1
SHA-12F6FCAEF15177DBBFE7F560E3870CA374B820EB3
SHA-256430B79A6D0BB30E0262D39B73ED54864353E5C94C62941F0E5A5837799EEF611