This bug was fixed in the package borgbackup - 1.0.7-0ubuntu1.16.04.1
---
borgbackup (1.0.7-0ubuntu1.16.04.1) xenial; urgency=high
* New upstream release, fixing security issues (LP: #1615380).
-- Gianfranco Costamagna Fri, 19 Aug 2016
21:52:22 +0200
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615380
Title:
[SRU] security issues on borgbackup
To manage notifications about this bug
so far so good!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615380
Title:
[SRU] security issues on borgbackup
To manage
Hello LocutusOfBorg, or anyone else affected,
Accepted borgbackup into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/borgbackup/1.0.7-0ubuntu1.16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Summary changed:
- security issues on borgbackup
+ [SRU] security issues on borgbackup
** Description changed:
- as explained here, upstream is asking to SRU borgbackup because of the fixes
below
+ [Impact]
+
+ * There are some fixes in repo corruption before 1.0.7
+ * There are some