Re: [Duplicity-talk] Why is passphrase required to write backups?

[James Utter]

Hi

> You did not mention what version you are currently running, but a lot
> has been fixed in the last few months.  Let me know how it goes.

Sorry - I realised that immediately after sending the message.  I was
running the dedian package of duplicity, version 0.4.3-4

I have since installed 0.4.4.RC3 (cannot find RC4 on the site)


On 24/10/2007, Kenneth Loafman <address@hidden> wrote:
> Welcome to the list.
>
> The the password prompt issue was fixed in 0.4.4.RC2.  RC4 is currently
> available at http://duplicity.nongnu.org/.  It will only ask for the
> password in cases where its needed.

--full suppresses the request for a passphrase (otherwise duplicity
still asks for it, even on a fresh backup), but the command is still
failing.

~$ duplicity --encrypt-key 82C98841 --full --exclude ~/Files/
/home/james/ scp://address@hidden:~/backup
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 400, in ?
    if __name__ == "__main__": main()
  File "/usr/bin/duplicity", line 389, in main
    if action == "full": full_backup(col_stats)
  File "/usr/bin/duplicity", line 146, in full_backup
    bytes_written = write_multivol("full", tarblock_iter, globals.backend)
  File "/usr/bin/duplicity", line 82, in write_multivol
    globals.gpg_profile,globals.volsize)
  File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 198,
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
510, 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 117, in write
    def write(self, buf): return self.gpg_input.write(buf)
IOError: [Errno 32] Broken pipe
close failed: [Errno 32] Broken pipe
close failed: [Errno 32] Broken pipe

Note: using a symmetric key does not fail.

Thanks,

James

P.S. It is slightly confusing that when not specifying a GPG Key,
(i.e. you are using symmetric encryption) you get the prompt "GnuPG
passphrase". Shouldn't it say "Symmetric passphrase:" ?

~$ duplicity   --exclude ~/Files/  /home/james/ scp://address@hidden:~/backup
GnuPG passphrase: