[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated

[Taylor Raack]

Brian, Sebastien, do either of you have the ability to mark this as a
bug in Bionic as well for tracking purposes? (I don't seem to have
permission to do that). It would be excellent for your patches to be
backported to Bionic, regardless of _who_ submits such a patch.

Thank you very much in advance!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1952107

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Triaged
Status in evolution-data-server source package in Focal:
  Triaged
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Taylor Raack]

I can also confirm that the network-manager package version
1.10.14-0ubuntu1 from bionic-proposed fixes the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  When using a VPN the DNS requests might still be sent to a DNS server
  outside the VPN when they should not

  * Test case

  Configure the system to send all the traffic to a VPN, do a name
  resolution, the request should not go to the public DNS server (to be
  checked by capturing the traffic by example with wireshark)

  
  * Regression potential

  The code change the handling of DNS servers when using a VPN, we
  should check that name resolution still work whne using a VPN in
  different configurations

  -

  
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp