Re: [Duplicity-talk] Timothy is your Yaar! :)

[Ingrid Lohmann]

Hello,

It's now working, but I use the same key for encryption and and signature, like 
so:  

duplicity --encrypt-key "53FG1V90" --sign-key "53FG1V90"  -v9 /home/mybackup  
scp://address@hidden//root 

is that a risk ?

in any event thank you for your help!

-------- Original-Nachricht --------
> Datum: Sat, 17 Nov 2007 09:43:58 -0600
> Von: Kenneth Loafman <address@hidden>
> An: Discussion of the backup program duplicity <address@hidden>
> Betreff: Re: [Duplicity-talk] Timothy is your Yaar! :)

> The error seems to be that the --encrypt-key is invalid.  I think you
> meant 123L76548 and not 123B76548 in your backup.sh script.
> 
> ...Ken
> 
> Ingrid Lohmann wrote:
> > Thanks a lot for your fast answer!
> > I added th option -v9. Below I post the resulting error message. I would
> be grateful if you can help me one more time. I think it has to do with
> the authentication process ?
> > 
> > #./backup.sh
> > error message: ---start---
> > 
> > Main action: inc
> > Reading results of 'printf 'cd /root
> > ls -1' | sftp -b - address@hidden'
> > Ignoring file 'blubber.tar.gz'
> > Ignoring file 'some_Backup'
> > Ignoring file 'backups'
> > Ignoring file 'oreono'
> > Collection Status
> > -----------------
> > Connecting with backend: scpBackend
> > Archive dir: None
> > No backup chains with active signatures found
> > 
> > Found 0 backup chains without signatures.
> > No orphaned or incomplete backup sets found.
> > No signatures found, switching to full backup.
> > Selecting /home/mybackup
> > Comparing () and None
> > Getting delta of (() /home/mybackup dir) and None
> > Generating delta - new file: .
> > Selecting /home/mybackup/.bash_history
> > Comparing ('.bash_history',) and None
> > Getting delta of (('.bash_history',) /home/mybackup/.bash_history reg)
> and None
> > Generating delta - new file: .bash_history
> > gpg: 59EDEC59: There is no assurance this key belongs to the named user
> > gpg: [stdin]: sign+encrypt failed: unusable public key
> > gpg: 59EDEC59: There is no assurance this key belongs to the named user
> > gpg: [stdin]: sign+encrypt failed: unusable public key
> > Selecting /home/mybackup/.bash_logout
> > Comparing ('.bash_logout',) and None
> > Getting delta of (('.bash_logout',) /home/mybackup/.bash_logout reg) and
> None
> > Generating delta - new file: .bash_logout
> > Selecting /home/mybackup/.bash_profile
> > Comparing ('.bash_profile',) and None
> > Getting delta of (('.bash_profile',) /home/mybackup/.bash_profile reg)
> and None
> > Generating delta - new file: .bash_profile
> > Selecting /home/mybackup/.bashrc
> > Comparing ('.bashrc',) and None
> > Getting delta of (('.bashrc',) /home/mybackup/.bashrc reg) and None
> > Generating delta - new file: .bashrc
> > Traceback (most recent call last):
> >   File "/usr/bin/duplicity", line 373, in ?
> >     if __name__ == "__main__": main()
> >   File "/usr/bin/duplicity", line 366, in main
> >     if not sig_chain: full_backup(col_stats)
> >   File "/usr/bin/duplicity", line 142, in full_backup
> >     bytes_written = write_multivol("full", tarblock_iter,
> globals.backend)
> >   File "/usr/bin/duplicity", line 78, in write_multivol
> >     globals.gpg_profile)
> >   File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 213, in
> GPGWriteFile
> >     try: data = block_iter.next(bytes_to_go).data
> >   File "/usr/lib/python2.4/site-packages/duplicity/diffdir.py", line
> 407, in next
> >     result = self.process(self.input_iter.next(), size)
> >   File "/usr/lib/python2.4/site-packages/duplicity/diffdir.py", line
> 487, in process
> >     data, last_block = self.get_data_block(fp, size - 512)
> >   File "/usr/lib/python2.4/site-packages/duplicity/diffdir.py", line
> 509, in get_data_block
> >     if fp.close(): raise DiffDirException("Error closing file")
> >   File "/usr/lib/python2.4/site-packages/duplicity/diffdir.py", line
> 347, in close
> >     self.callback(self.sig_gen.getsig(), *self.extra_args)
> >   File "/usr/lib/python2.4/site-packages/duplicity/diffdir.py", line
> 298, in callback
> >     sigTarFile.addfile(ti, cStringIO.StringIO(sig_string))
> >   File "/usr/lib/python2.4/site-packages/duplicity/tarfile.py", line
> 768, in addfile
> >     copyfileobj(fileobj, self.fileobj, tarinfo.size)
> >   File "/usr/lib/python2.4/site-packages/duplicity/tarfile.py", line
> 198, in copyfileobj
> >     dst.write(buf)
> >   File "/usr/lib/python2.4/site-packages/duplicity/dup_temp.py", line
> 120, in write
> >     return self.fileobj.write(buf)
> >   File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 103, in
> write
> >     def write(self, buf): return self.gpg_input.write(buf)
> > IOError: [Errno 32] Broken pipe
> > close failed: [Errno 32] Broken pipe
> > 
> > ---end---
> > 
> > "backup.sh" includes:
> > --start---
> > #!/bin/bash
> > export PASSPHRASE=signtest
> > duplicity --encrypt-key "123B76548" --sign-key "J87VD263"  -v9
> /home/mybackup  scp://address@hidden//root
> > ---end---
> > 
> > 
> > 'gpg --list-keys' delivers
> > 
> > /root/.gnupg/pubring.gpg
> > ------------------------
> > pub   1024D/ZZZ27E0F 2007-11-13 [expires: 2008-11-12]
> > uid                  backuptest (backuptest)
> >  <address@hidden>
> > sub   1024g/1231F6EB 2007-11-13 [expires: 2008-11-12]
> > 
> > pub   1024D/55B4AB15 2007-11-13 [expires: 2008-11-12]
> > uid                  backuptest (backuptest)
> >  <address@hidden>
> > sub   1024g/7UUU4EF8 2007-11-13 [expires: 2008-11-12]
> > 
> > pub   1024D/123L76548 2007-11-13 [expires: 2008-11-12]
> > uid                  signtest (signtest) 
> > <address@hidden>
> > sub   1024g/6DDE2F16 2007-11-13 [expires: 2008-11-12]
> > 
> > pub   1024D/J87VD263 2007-11-13 [expires: 2008-11-12]
> > uid                  backuptest (backuptest) 
> > <address@hidden>
> > sub   1024g/59EDEC59 2007-11-13 [expires: 2008-11-12]
> > 
> > 
> > ok much stuff to read... if you (anybody else) can tell
> > me, how to overcome the probably stupid mistake , I
> > would be gratefull.
> > 
> > regards!
> > 
> > 
> > 
> > 
> > 
> > -------- Original-Nachricht --------
> >> Datum: Fri, 16 Nov 2007 14:03:44 -0600
> >> Von: Kenneth Loafman <address@hidden>
> >> An: Discussion of the backup program duplicity
> <address@hidden>
> >> Betreff: Re: [Duplicity-talk] Timothy is your Yaar! :)
> > 
> >> Ingrid Lohmann wrote:
> >>> I'm sorry for foolish question...
> >>>
> >>> but I have serious beginner problems with duplicity. 
> >> That's what the list is for, and its not foolish to ask.
> >>
> >>> Please Can can you put me back on the list ?
> >> You were never removed, only address@hidden, the one that sent the
> >> spam.  I guess I should not have replied to the whole list.
> >>
> >>> I installed duplicity according to the following howto:
> >>> http://www.debian-administration.org/articles/209
> >> I did not know about that howto.  I appreciate the info!  Its good.
> >>
> >>> if I start duplicity with this script:
> >>> #!/bin/bash
> >>> export PASSPHRASE=signtest
> >>> duplicity --encrypt-key "111A0168" --sign-key "D21AV63" /home/mybackup
> >> scp://address@hidden//root
> >>>   
> >>> I get the following error message
> >>> ---begin---
> >> This looks like it should work.  What version are you running?
> >>
> >> The error you need to process may be between the command line and the
> >> start of the traceback.  If not, please rerun and add '-v9' to the
> >> command line, then post all of the messages from the command line down.
> >>
> >> ...Thanks,
> >> ...Ken
> >>
> >>
> > 
> 
> 

-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail