Result for 076EB67E59E09772C39FCD71D25542142BF9684A

Query result

Key Value
FileName./usr/lib64/python2.7/site-packages/duplicity/_librsync.so
FileSize17112
MD56BED8F978A335EA26098D2EF00FEAE2D
SHA-1076EB67E59E09772C39FCD71D25542142BF9684A
SHA-25615804896CFC1018039C7984F08CB10435B1CB0D3ED5F5C8D0A989C7022647986
SSDEEP192:l9B41KEVc5r7hMG0rkTt5PQdtV9J+dOPy9rcZPCxOivwH9aWwFcXEnurrhw:lL0d9JrIQdhq9rcZqxOiIdY2
TLSHT1227263D37B448917D91B0E7188CB3776DBAC44144E9E3223A30E2AAB1493754FE39D5A
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
MD5402F78BBE35C5800E6C13A5F4977567F
PackageArchppc64
PackageDescriptionDuplicity incrementally backs up files and directory by encrypting tar-format volumes with GnuPG and uploading them to a remote (or local) file server. In theory many protocols for connecting to a file server could be supported; so far ssh/scp, local file access, rsync, ftp, HSI, WebDAV and Amazon S3 have been written. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Currently duplicity supports deleted files, full unix permissions, directories, symbolic links, fifos, device files, but not hard links.
PackageMaintainerKoji
PackageNameduplicity
PackageRelease1.fc16
PackageVersion0.6.14
SHA-18F329DD847C1219440513B454318410ED5DC591A
SHA-2561D513032C2236AD12C07B4A9B751F3ACF18D19FA42F9147B914B868B22F4C502