This bug was fixed in the package deja-dup - 37.1-2fakesync1ubuntu0.2
---
deja-dup (37.1-2fakesync1ubuntu0.2) bionic; urgency=medium
* debian/patches/invalid_password_handling.patch:
- handle correctly when an invalid password is entered
(lp: #918489)
-- Sebastien
I tested this and it worked!
- Made an initial backup, not saving password.
- Backed up again, changing the password.
With the old version, I got an error at "verify the backup" step. But
the backup files did end up being written with the wrong password.
With the new version, it did not accept
From a quick glance at the code, Xenial doesn't look fixed to me. Bionic
has the issue and so the SRU for Bionic is correct. Focal has the issue
fixed.
Since Xenial is past the end of standard support I expect it won't be
fixed for this issue anyway, but I'm just noting that the bug status may
be
** Changed in: deja-dup (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918489
Title:
duplicity allows a new, different passphrase if an
Upstream closed the duplicity task without details so let's assume it's
fixed in the current version and Ubuntu serie
** Changed in: duplicity (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
** Changed in: duplicity (Ubuntu)
Status: Triaged => Fix Released
** Changed in: deja-dup
It escaped my attention at the time, but Ubuntu 18.04 released with both
a version of duplicity that shows the new incremental-backups-also-have-
this-issue behavior (see my comment 22) and a release of deja-dup that
wasn't yet fixed to avoid it.
Which means that deja-dup in Ubuntu 18.04 is still
** Changed in: duplicity
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918489
Title:
duplicity allows a new, different passphrase if an archive cache
IMHO: A backup software that has a "problem when restoring" is
completely worthless, not "another issue".
If you are doing an encrypted backup and somebody gets access to your
passphrase, the safe thing to do is create a completely new backup with
a new passphrase, and wipe (and destroy) all
Although comment 22 is IMHO a duplicity bug, the fact that you can do a
full backup with a new passphrase is, for me, a feature. If somebody had
access to your passphrase, the safe thing to do is to rotate it, do a
full backup, and stick with the new one from there onwards.
There's a problem
** Changed in: duplicity
Status: New => Confirmed
** Changed in: duplicity (Ubuntu)
Importance: Undecided => High
** Changed in: duplicity (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
10 matches
Mail list logo
