lp:~lekensteyn/duplicity/multipass
- Get this branch:
- bzr branch lp:~lekensteyn/duplicity/multipass
Branch merges
- Peter Wu (community): Needs Fixing
- duplicity-team: Pending requested
-
Diff: 314 lines (+116/-25)4 files modifiedduplicity-bin (+65/-18)
duplicity.1 (+30/-5)
duplicity/commandline.py (+3/-0)
duplicity/gpg.py (+18/-2)
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 |
Related blueprints
Recent revisions
- 725. By Peter Wu
-
- 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
-
- 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
-
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 - 719. By Kenneth Loafman
-
Boto has refactored too many times, so back off and just use Exception rather than searching.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:duplicity/0.6