Re: New crypto in 2.3.4

Denis Corbin <[email protected]> Tue, 24 Jul 2007 08:35:21 +0200
Newsgroups gmane.comp.sysutils.backup.dar.general
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Vasilevsky wrote:
> On 7/21/07, Denis Corbin <[email protected]> wrote:
>>
>> Well, here what is done in CVS and what will be available with release
>> 2.3.5 about this issue:
> 
> 
> The changes sound great. Just to confirm: With new versions of dar we will
> be able to specify '--key bfw:' to create an archive that is compatible
> with
> pre-2.3.4 versions and systems without evp/hmac. Is that correct?

Right. I have tested it. However, the archives generated by dar version
greater than or equal to 2.3.4 have a greater revision format than
archives generated by version 2.3.x where x < 4. Thus if you read with
release 2.3.x --- with x < 4 --- an archive generated by next to come
release 2.3.5 using "-K bfw:" this will trigger a warning telling that
the archive is too recent and asking whether to ignore this difference
or abort the operation. if you ignore the difference, you will be able
to read the encrypted archive.

> 
> Dave
> 
> 

Regards,
Denis.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGpZ2ppC5CI8gYGlIRAiNIAKC/8AyDWr3etQeRwI2Y2hsML11doACfX30A
o9EigpKoqSQg4jp05jtmGlg=
=pQxd
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/