Re: Version 0.16-beta2 released

[Shachar S. <rsy...@sh...>]

Tom Metro wrote:

>> 0.17 will have signing of the encrypted file...
>
> What do you mean by that? Given that a public key is involved, aren't
> they essentially signed now?

No, the public key is only used to encrypt the symmetric key right now.

Signing means that an automatic process can verify, without being able
to decrypt the package, that it was signed by a specific key. This is
important if you happen to create more than one backup copy, and want to
make sure that you are not backing up compromised data.

>> The only thing missing from this beta release before it can be called
>> "0.16" is deleting encrypted versions of deleted plain text files when
>> the file names are encrypted. This is not going to be very easy to
>> implement efficiently, so it will take a little time.
>
>
> Are you referring to a scenario in which you have a source directory
> with files a, b, and c. You process them through rsyncrypto and get 3
> encrypted files with encrypted file names. Then file b is deleted from
> the source directory, and rsyncrypto is called upon to process the
> directory again?

Yes.

> What is the problem? That it is inefficient to go through the list of
> files in the destination directory, map their file names back to the
> unencrypted names, and check to see if the source files still exist?

It's not difficult for the "recursive" case. It is, however, difficult
when you use the "filelist" option, and some of the files you mention in
the file list are directories. In such a case, if file names are
encrypted, all files from all directories find their way to the same
directory. This means that we need to keep track which file came from
which directory. Not a huge task, but also not a straight forward one.

>  -Tom

Shachar


-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html