Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:xxxx/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work.
Thank you! A patch would be most welcome, as we can't update to 43.x in <f36 because of a lack of gtk4.
Created attachment 1881487 [details] Backported fix for 42.8 Here is a backported patch for 42.8 in F35 (minus some cleanup that doesn't matter for a backport). I've briefly tested it but still. Any extra QA welcome. One for 42.7 in F34 coming as well.
Created attachment 1881488 [details] Backported fix for 42.7
FEDORA-2022-07c5ceed0c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-07c5ceed0c
FEDORA-2022-a8e368d55d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a8e368d55d
Thank you so much!
FEDORA-2022-a8e368d55d has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a8e368d55d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a8e368d55d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-07c5ceed0c has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-07c5ceed0c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-07c5ceed0c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-07c5ceed0c has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-a8e368d55d has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.