rsyncrypto
Rsyncrypto allows you to encrypt a file or a directory structure such that they can later be synchronized to another machine using rsync. This means that local changes to the plain text file result in local changes to the cipher text file. rsyncrypto compresses the plain text file prior to encrypting it with gzip using the "rsyncable" patch, which is available from the rsync sources.
| Tags | Information Management Document Repositories Security Cryptography Archiving backup Mirroring Systems Administration Utilities |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX Linux Windows Windows |
| Implementation | C++ |
Recent releases
- 24 Jul 2008 00:38
Changes: Creation of files in a safe way. Better error reporting on Windows.
- 24 Jun 2008 21:00
Changes: A segfault when the private key is needed but not available has been fixed. On Vista, symbolic links are identified (and ignored). This release will not terminate as soon as an error occurs, but will continue at the next reasonable operation.
- 23 May 2008 20:24
Changes: This release adds an option "--export-changes" that writes to a log file the files affected by the operation in a way suitable for passing to rsync's --include-from option. On Windows, mkdir would still fail if the last component of the path to create was a drive letter; this has been fixed.
- 15 May 2008 13:25
Changes: A serious bug was fixed: when deleting an entire directory with --name-encrypt and --delete-keys, rsyncrypto (since 1.07) would leave a corrupt filemap behind. The "rsyncrypto_recover" tool was added, which fixes the corruption caused by the above bug.
- 11 May 2008 08:35
Changes: When a directory turns into a file with --name-encrypt and --delete, rsyncrypto would terminate with an error. This release ensures that using a preexisting empty filemap does not crash rsyncrypto. -d with --filelist with stdin as input created an erronous "need --no-archive-mode"; this has been fixed. The mkdir error on Win32 is really fixed this time. --ne-nesting would cause --delete and --delete-keys to delete the wrong path (and thus fail); this has been fixed.
