lp:~lekensteyn/duplicity/multipass

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:duplicity/0.6 at revision 750

Peter Wu (community): Needs Fixing on 2011-06-12

duplicity-team: Pending requested 2011-06-11

Diff: 314 lines (+116/-25)

4 files modified

duplicity-bin (+65/-18)
duplicity.1 (+30/-5)
duplicity/commandline.py (+3/-0)
duplicity/gpg.py (+18/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #680425: Endless retype passphrase when typo	Medium	Fix Released
Bug #793096: Allow to pass different passwords for --sign-key and --encrypt-key	Medium	Fix Released

Link a bug report

Related blueprints

725. By Peter Wu on 2011-06-17

- duplicity.1: move information about the PASSPHRASE and SIGN_PASSPHRASE
  environment variables to the Environment Variables section
- duplicity.1: add information about the limitation on using
  symmetric+sign to the bugs section
- In the passphrase retrieval function get_passphrase, do not switch from
  "ask password without verifying" to ask+verify if the passphrase was
  empty
- Allow an empty passphrase for signing key
- Make clear in the verification prompt whether the encryption passphrase
  or the signing passphrase is being confirmed
- Fix passphrase retrieval for sym+sign (duplicity-bin and gpg.py)
- Allow sym+sign with limitation (see comments and manual page)

724. By Peter Wu on 2011-06-11

- invalid function description fixed for get_passphrase in duplicity-bin
- function get_passphrase in duplicity-bin accepts argument "for_signing"
  which indicates that a passphrase for a signing key is requested
- introduces the SIGN_PASSPHRASE environment variable for passing a
  different passphrase to the signing key
- commandline option --encrypt-secret-keyring=path introduced to set a
  custom location for the secret keyring used by the encryption key
- manual page updated with SIGN_PASSPHRASE and --encrypt-secret-keyring
- ask for a new passphrase if the passphrase confirmation failed to
  prevent an endless retype
- improved some comments in the code
- due to the difference in the handling of the signing and encryption
  passphrase, the passphrase is asked later in the duplicity-bin

723. By edso on 2011-05-11

as restoring is non-destructive by default (overideable with --force) there is no need to raie fata errors if not supported in/exclude parameters are given as parameters.
see also:
http://lists.gnu.org/archive/html/duplicity-talk/2011-04/msg00010.html

722. By Kenneth Loafman on 2011-04-16

Insure Python 2.4 compatible.

721. By Kenneth Loafman on 2011-04-16

433591 AttributeError: FileobjHooked instance has no attribute 'name'

720. By Kenneth Loafman on 2011-04-04

Merged in lp:~ed.so/duplicity/0.6-add_sftp.

719. By Kenneth Loafman on 2011-04-04

Boto has refactored too many times, so back off and just use Exception rather than searching.

718. By Kenneth Loafman on 2011-04-03

Boto moved S3ResponseError, so allow for different imports.

717. By Kenneth Loafman on 2011-04-02

Changes for 0.6.13.

716. By Kenneth Loafman on 2011-04-02

Changes for 0.6.13.