Re: Typo Report in Man Page - "fro stdin" and Question
Brought to you by:
thesun
From: Shachar S. <sh...@sh...> - 2012-06-21 17:49:08
|
On 06/21/2012 06:06 PM, Shlomi Fish wrote: >> But despair not. You can achieve the equivalent level of security by >> encrypting your private key with a password, and storing it using the >> same provider you store your actual data. At this point in time >> rsyncrypto does not support decrypting from password protected RSA keys, >> but such support can be, fairly easily, added. Otherwise, in case of >> catastrophe, you can simply pull your encrypted key and decrypt is locally. >> > Thanks! I think that is also what Harold suggested. Same end result, give or take. Different mechanism. RSA keys can be encrypted via a fairly standard fashion that has nothing to do with pgp or gpg. Openssl knows how to open such encrypted keys, and so will a future version of rsyncrypto. > > BTW, do you think it would be possible to write an --rsyncable patch for xz > instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz ) I think you meant LZMA. After spending a couple of minutes reading on it, my gut feeling is that turning it rsyncable in any meaningful way will greatly hurt the compression ratios you're used to seeing from it, negating the reason you wanted to use it to begin with. It achieves better compression ratios by having a very big lookback buffer (encoded as a dictionary), which is the exact opposite of rsyncability. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com |