Re: [Duplicity-talk] Integrity check

[edgar . soldin]

Jacob, unfortunately the script will not know about deleted chains. How 
do you deal with that?
And didn't Ken wrote that there are checksums in the manifest files?

Also I just checked and see that the gpg files produced duplicity are 
signed. Therefore for integrity checking they only have to be decrypted 
and the output checked for the 'good signature' line. Unfortunately the 
'gpg --verify' command seems to only work with detached signatures. I 
could do it in duply, but I feel it belongs in duplicity as 
'integrity-check'. Maybe I'll check if I can strip down the duplicity 
verify command to unpack only and then insert this as the new command 
subroutine.

.. ede

On 17.09.2009 11:41, László Monda wrote:
> On Tue, Sep 15, 2009 at 7:00 PM, Jacob Godserv<address@hidden>  wrote:
> > On Tue, Sep 15, 2009 at 03:46, László Monda<address@hidden>  wrote:
> > > Hi List,
> > >
> > > How is it possible to do integrity check with duplicity on backed up
> > > content?  The verify action compares content, but it's not explicitly
> > > for integrity checks, right?
> > >
> > > Thanks in advance!
> >
> > I always generate sha512sums after each backup, with something like
> > following script. This only runs in Linux environment.
> >
> > --------------------
> > files=$(find -name 'duplicity*gpg')
> >
> > for file in ${files}; do
> >         sha512_dir=$(dirname "${file}")"/.sha512sums/"
> >         if [[ ! -d "${sha512_dir}" ]]; then mkdir "${sha512_dir}" || exit 1; fi
> >         file_checksum="${sha512_dir}"$(basename "${file}")".sha512sum"
> >
> >         if [[ ! -e "${file_checksum}" || ! -s "${file_checksum}" ]]; then
> >                 echo "Generating checksum for ${file} and storing in
> > ${file_checksum}..."
> >                 sha512sum ${file}>  "${file_checksum}"
> >         fi
> > done
> > --------------------
> >
> > I can them check the sums by running the following command:
> > # sha512sum -c .sha512sums/*
> >
> > Or I can check something specific like this:
> > # sha512sum -c .sha512sums/duplicity-full-signatures.DATETZ.sigtar.gpg.sha512sum
> >
> > Something like that would verify that the backup data is intact.
>
> Sounds good, however it'd be very nice to have an integrity-check
> action specifically for this task.
>
> >