Result for 933AFE3D8B6A8982C01F1D257FAF67682AB9F9B5

Query result

Key Value
FileName./usr/bin/mirror-registry
FileSize9130960
MD5766935D10CF33935EC05EFE46A3E3FC5
SHA-1933AFE3D8B6A8982C01F1D257FAF67682AB9F9B5
SHA-256510BB7ADD1ED052405A4B6039D6AA104B19B71B1A54111E99B0DE3F7C6B306E9
SSDEEP49152:0Ibkj5N+PCiejANituiQ4DAWXVc09psd5EzgRNEyfJ+dfmVvDgTkv88mSVxXoGip:0ISkPXliYRNEznT9YWn
TLSHT11C96E8C199A1C34AD63DAD31EFE6AFE8E66A2E335D84554EC5C8F33D3D7217080A9460
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
MD5252F7B28058AED2A671BDD78DF5AED20
PackageArchs390x
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp156.1.14
PackageVersion1.4
SHA-1AB933B1CD0D48D5B23DF6BF7EB00C13838797736
SHA-256FAD1D558F8AC103D7F02C9DADFE6A7AE30825E5A312943C2C2CA7FA2DDB5997E