backup without private key
Bug #687295 reported by
edso
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Read more here
http://
Summary is:
currently this works only on english systems by silently ignoring the absence of the secret key for archive-dir comparision.
short term Solution might be:
a language independent (gpg --status-fd) catching of the error
a parameter switch (e.g. --no-secret-key) with proper documentation about the pros & cons
long term Solution should be:
a hashing comparision of remote and local archive-dir circumventing the need for decryption
more info is found on the thread linked above
[Duplicity-talk] duplicity incr - private key missing
..ede/duply.net
Changed in duplicity: | |
importance: | Undecided → Medium |
milestone: | none → 0.8.00 |
status: | Confirmed → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It is correct INC backup without the private key is not working for me as well.
This makes me wonder why bother to have the --encrypt-key and --sign-key option.
Thsi would be an excellent setup to protect the encryption of the backup making sure backup private key is never exposed and haveing a second signing key which in worst will be compromised.
The Privacy of the Backup however would be granted.
I would be thrilled if the above discribed solution (hashing) could be implemented.