Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] encryption and rsync



On 7/16/2012 1:59 AM, Tom Metro wrote:
> But I'm assuming that EncFS isn't doing anything to assist the syncing
> of partial files, so your minimum transfer is a full file.

Like I said, I've been experimenting, and I've found how to make this 
work better with rsync/unison.  Hooray for reading the manual :).

EncFS has an option called per-file initialization vectors (IVs) which 
is enabled by default.  This option generates a 64-bit random IV for 
each file written.  This ensures that encrypted blocks are never 
identical.  If you turn per-file IVs off then block encryption becomes 
deterministic, which is a fancy way of saying same cleartext in, same 
ciphertext out.

rsyncrypto uses the same kind of not-random IVs with similar results.

-- 
Rich P.




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org