| Key | Value |
|---|---|
| FileName | ./usr/lib64/python2.6/site-packages/duplicity/backends/__init__.pyo |
| FileSize | 379 |
| MD5 | 3477994785971E3942A7C58E8C49DD4D |
| SHA-1 | 14622D4F80CC310B08A7482D9DFDEF04AECE9F8B |
| SHA-256 | 0D5643C1B6F0C2DBD81CFE4D4AA9D6F9631E6AB183D1801A563F92780DA312DB |
| SSDEEP | 6:u5hCev/sR34cAkldhCuBhtKLQJ+am6SSHWrBq3/4GekMOXrmOjncRa+X:5ev/IIIb5BhtKb73HVw/4GekMZOjncge |
| TLSH | T102E0208863F572EFDF3E44B2F5524367C7BD546FA2171750606C015D1DCC1540A76A4D |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
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 |
|---|---|
| MD5 | 2A86763127C6CE6ABBFECC9049E1C1B0 |
| PackageArch | sparc64 |
| PackageDescription | Duplicity 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. |
| PackageMaintainer | Fedora Project |
| PackageName | duplicity |
| PackageRelease | 1.fc12 |
| PackageVersion | 0.6.05 |
| SHA-1 | B64583EB80E8C4EABE3C7A0B79142919BA76C6BA |
| SHA-256 | 1FE51E5BCC9A9AD8C89338AC5677DDECB6C1E2777642F8446DE00589A096621D |