See also LP:2009756 & https://github.com/bit-team/backintime/issues/1247
** Bug watch added: BackInTime Issues #1247
https://github.com/bit-team/backintime/issues/1247
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync
As this is working as expected, I am marking this bug as "invalid".
Thanks!
** Changed in: rsync (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launc
I can confirm the scenario described in comment #5 is what is causing
the issue. There are two ways to correctly fix it: 1- ask for the right
directory that matches the forced command, or 2- use the new --old-args
option that was backported to the security update, that should bypass
the new securit
Jammy's rsync (3.2.7) has --trust-sender that's described as: "trust the remote
sender's file list"
However that won't be of much help as that's not available in older releases :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
So after looking further into the way the systems affected by this issue
are configured, this is what is happening:
1- rsync client is requesting a directory: rsync -v -rp
sshuser@server:/var/cache/foo /tmp/foo
2- the server has an ssh forced command configured that is returning the
contents of
I'm going to need a reproducer for this issue so I can figure out what's
not working in your specific example.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009575
Title:
Provided requested details privately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009575
Title:
Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
Status in rsync package
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009575
Title:
Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
Sta
I need to see the filenames that got rejected. You can send them to me
in private is required. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009575
Title:
Upgrade
** Description changed:
Hi
- Several systems upgraded their rsync package from 3.1.3-8ubuntu0.4 to
- 3.1.3-8ubuntu0.5 overnight.
+ Several systems running Ubuntu 20.04 upgraded their rsync package from
+ 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight.
- Automated syncs are now failing with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsync (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/b
11 matches
Mail list logo
