This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug. This will ensure that all associated bugs get updated
when new packages are pushed to stable.
# bugfix, security, enhancement, newpackage (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi update submission link instead:
Could you please fix this soon?
Please see bug #1126712 at comment #13 and let us follow up this there. I do
not have any new status - except I overlooked something.
Thanks so much for the details. It seems the patches have been merged in one of the branches of upstream author Martin Pool
Let's hope a new release comes out soon.
(In reply to pjp from comment #4)
> Let's hope a new release comes out soon.
@Robert: could you please check with Martin about a new release or if they have snapshot releases?
(In reply to pjp from comment #5)
> @Robert: could you please check with Martin about a new release or if they
> have snapshot releases?
Meanwhile there is a new librsync release, I notified package owners whose
packages depend on librsync about the upcoming change (ABI incompatibility).
librsync-1.0.0-1.fc22,csync2-1.34-15.fc22,duplicity-0.6.25-2.fc22,rdiff-backup-1.2.8-14.fc22 has been submitted as an update for Fedora 22.
librsync-1.0.0-1.fc21,csync2-1.34-15.fc21,duplicity-0.6.25-3.fc21,rdiff-backup-1.2.8-14.fc21 has been submitted as an update for Fedora 21.
librsync-1.0.0-1.fc20,csync2-1.34-15.fc20,duplicity-0.6.25-3.fc20,rdiff-backup-1.2.8-14.fc20 has been submitted as an update for Fedora 20.
csync2-1.34-15.fc22, rdiff-backup-1.2.8-14.fc22, librsync-1.0.0-1.fc22, duplicity-0.6.25-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
librsync-1.0.0-1.fc20, duplicity-0.6.25-3.fc20, csync2-1.34-15.fc20, rdiff-backup-1.2.8-14.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
csync2-1.34-15.fc21, rdiff-backup-1.2.8-14.fc21, librsync-1.0.0-1.fc21, duplicity-0.6.25-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.