Actually to clarify - what I want to do is to be able to read the
associated checksums ZFS creates for a file and then store them in an
external system e.g. an oracle database most likely

Its just a way of avoiding having to do MD5's on everything when ZFS is
doing checksums as well.

If ZFS does block level checksums, then I guess that's not so easy to
use them in that way.

I will check out the crypto extensions when they become available.

Thanks


>Brant Bady
>Access and Information Management
>Royal British Columbia Museum
>Telephone:  (250) 387-4126
>Email:  [EMAIL PROTECTED]
>
>

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 14, 2006 1:46 PM
To: Henk Langeveld
Cc: Bady, Brant RBCM:EX; zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] Access to ZFS checksums would be nice and
very useful feature


On Sep 14, 2006, at 1:32 PM, Henk Langeveld wrote:

> Bady, Brant RBCM:EX wrote:
>> Part of the archiving process is to generate checksums (I happen to 
>> use MD5), and store them with other metadata about the digital object

>> in order to verify data integrity and demonstrate the authenticity of

>> the digital object over time.
>
>> Wouldn't it be helpful if there was a utility to access/read  the 
>> checksum data created by ZFS, and use it for those same purposes.
>
> Doesn't ZFS use block-level checksums?
>> Hoping to see something like that in a future release, or a command 
>> line utility that could do the same.
>
> It might be possible to add a user set property to a file with the 
> md5sum and a timestamp when it was computed.
>
> But what would this protect against?  If you need to avoid tampering, 
> you need the checksums offline anyway - cf. tripwire.
>
> Cheers,
> Henk
>

Better still would be the forthcoming cryptographic extensions in some
kind of digital-signature mode.

ckl


_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to