Murk is a Unix-based encryption software that allows for friendly synchronization using rsync command line. It provides a secure way to transfer data files over the internet, ensuring data privacy and integrity.
Murk is a powerful encryption software that runs smoothly on the UNIX command line. It offers unparalleled security and is compatible with rsync, making it a great tool for data transfer. In terms of efficiency, however, using murk with rsync under specific conditions is recommended.
When transferring data with rsync, murk requires the uncompressed files to be compressed with bzip2 before encryption via mcrypt -p. On plain rsync, the transfer rate for a 15418880-byte file such as openssl-0.9.7e.tar is 4353737 bytes. Using mcrypt -p followed by rsync results in a transfer rate of 2452373 bytes, while using murk followed by rsync yields 3570755 bytes.
Although murk and rsync on uncompressed data cannot compete with well-compressed files, the difference in transfer rates between murk and plain rsync is negligible when the data is nicely compressible. Even if the compression hinders the efficiency of rsync, the compressed file is still smaller than the uncompressed deltas.
In a backup scenario where small changes are made to large data pieces, murk can be incredibly useful. Consider a folder with 600MB of data containing a new 100K manual. Plain rsync transfers at a rate of 110192 bytes, while using mcrypt -p followed by rsync results in a transfer rate of 80754324 bytes. On the other hand, murk followed by rsync transfers at a rate of 119486 bytes.
The latest version of murk features fixes after running Valgrind, changes in the initialization vector with each new block, and improvements in building with ctags. Additionally, the README includes a disclaimer to address a suggestion from freshmeat comments.
When transferring data with rsync, murk requires the uncompressed files to be compressed with bzip2 before encryption via mcrypt -p. On plain rsync, the transfer rate for a 15418880-byte file such as openssl-0.9.7e.tar is 4353737 bytes. Using mcrypt -p followed by rsync results in a transfer rate of 2452373 bytes, while using murk followed by rsync yields 3570755 bytes.
Although murk and rsync on uncompressed data cannot compete with well-compressed files, the difference in transfer rates between murk and plain rsync is negligible when the data is nicely compressible. Even if the compression hinders the efficiency of rsync, the compressed file is still smaller than the uncompressed deltas.
In a backup scenario where small changes are made to large data pieces, murk can be incredibly useful. Consider a folder with 600MB of data containing a new 100K manual. Plain rsync transfers at a rate of 110192 bytes, while using mcrypt -p followed by rsync results in a transfer rate of 80754324 bytes. On the other hand, murk followed by rsync transfers at a rate of 119486 bytes.
The latest version of murk features fixes after running Valgrind, changes in the initialization vector with each new block, and improvements in building with ctags. Additionally, the README includes a disclaimer to address a suggestion from freshmeat comments.
What's New
Version 0.3: N/A