swell.k at gmail.com
Fri Apr 17 21:56:08 UTC 2009
Tim Kientzle <kientzle at freebsd.org> writes:
> Mel Flynn wrote:
>> On Friday 17 April 2009 19:52:36 Tim Kientzle wrote:
>>> This should be fixed in SVN r191196 by my update to
>>> lib/libarchive/config_freebsd.h, which disabled the
>>> crypto references here until I can sort out some
>>> other issues.
>> It's fixed. What should we be looking for (if anything) that's now
>> broken with crypto references disabled?
> Specifically, I (temporarily) disabled libarchive's
> ability to generate cryptographic hashes when writing
> mtree format.
> This is a new feature that nobody knows about, so I
> doubt it will affect you. ;-) When I re-enable it,
> you should be able to:
> tar -cf - --format=mtree --options=sha512 .
> and generate an mtree file with sha512 checksums.
> No big deal, of course, since mtree does this even better.
> Here's something mtree can't do, though:
> tar -cf - --format=mtree --options=sha512 @file.tgz
> to generate an mtree file (with sha512 checksum info)
> of the contents of a tar file.
> Of course, libarchive's mtree support is mostly for
> developers to use in building new tools that use
> mtree format in innovative ways. Exposing it through
> tar is primarily to make it easier to test.
Can you document mtree writing support in libarchive‐formats(5) ?
Ah, and fix section in that file, too
.Dt libarchive-formats 3
> P.S. I just realized that I probably broke WITHOUT_OPENSSL
> builds as well. I'm running a series of buildworlds
> today to try to verify all of this; I hope to
> have it all settled within 24 hours. Apologies for
> the turmoil.
More information about the freebsd-current