[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Steve Langasek]

The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Released
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions


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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Changed in: lightdm (Ubuntu Wily)
 Assignee: Robert Ancell (robert-ancell) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Released
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.14.4-0ubuntu1

---
lightdm (1.14.4-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Handle XDMCP Request packet with no addresses. (LP: #1516831)
- Don't start LightDM if the XDMCP server is configured with a key that
  doesn't exist. (LP: #1517685)
- Add IP addresses to XDMCP log messages.
- Refactor XDMCP error handling.
- Add more tests.

 -- Robert Ancell   Fri, 20 Nov 2015
16:01:15 +1300

** Changed in: lightdm (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Released
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.10.6-0ubuntu1

---
lightdm (1.10.6-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Handle trailing whitespace on boolean values in configuration.
  (LP: #1507033)
- Use libaudit to generate audit events.
- Fix apparmor profiles for running Chromium in guest sessions.
  (LP: #1504049)
- Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and
  LC_IDENTIFICATION variables to the list of inherited locale variables.
  (LP: #1511259)
- Add a backup-logs option that can be used to disable existing logging
  files having a .old suffix added to them.
- Check the version of the X server we are running so we correctly pass
  -listen tcp when required. (LP: #1449282)
- Use IP address of XDMCP requests to contact X server if available.
  (LP: #1481561)
- Implement XDMCP ForwardQuery. (LP: #1511545)
- Add an option for XDMCP and VNC servers to only listen on one address.
  (LP: #1390808)
- Don't start LightDM if the XDMCP server is configured with a key that
  doesn't exist. (LP: #1517685)
- Add IP addresses to XDMCP log messages.
- Refactor XDMCP error handling.
- Fix small memory leak in XDMCP logging code.
- Fix typo in dm-tool man page. (LP: #1470587)
- Use new Xmir binary when running X under Unity System Compositor.
- Fix all the things that prevent clang (3.5) from building LightDM with
  -Werror.
- Add more tests.

 -- Robert Ancell   Fri, 20 Nov 2015
16:07:50 +1300

** Changed in: lightdm (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Tags removed: verification-needed
** Tags added: verification-done-trusty verification-needed-vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Changed in: lightdm (Ubuntu Trusty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm (Ubuntu Wily)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Chris J Arges]

Hello Robert, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Mathew Hodson]

** Changed in: lightdm (Ubuntu Precise)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Also affects: lightdm (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Also affects: lightdm (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: lightdm (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Wily)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Chris J Arges]

** Tags removed: verification-done-vivid
** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

This change caused bug 1516831

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Tags removed: verification-needed
** Tags added: verification-done-vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Brian Murray]

Hello Robert, or anyone else affected,

Accepted lightdm into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.14.3-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Vivid)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Description changed:

- Currently LightDM connects to an XDMCP enabled X server using the first
- suitable address in the XDMCP Request packet. However, some clients may
- put a number of addresses in this message and potentially they are not
- all routable. If the address the request message came from is in the
- list we should use that first as that is more likely to be a routable
- address. This also matches the behaviour of GDM which ignores the
- contents of the Request packet anyway.
+ [Impact]
+ Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.
+ 
+ [Test Case]
+ 1. Start LightDM with XDMCP enabled
+ 2. Connect with a client that puts a number of addresses in the Request packet
+ 
+ Expected result:
+ LightDM prefers the address the Request came from over the other addresses.
+ 
+ Observed result:
+ LightDM always picks the first address.
+ 
+ [Regression Potential]
+ There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

** Changed in: lightdm/1.14
   Status: Fix Committed => Fix Released

** Also affects: lightdm (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu Vivid)
   Status: New => Triaged

** Changed in: lightdm (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Triaged

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Changed in: lightdm (Ubuntu Vivid)
   Status: Triaged => In Progress

** Changed in: lightdm (Ubuntu Vivid)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  In Progress

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.15.1-0ubuntu1

---
lightdm (1.15.1-0ubuntu1) wily; urgency=medium

  * New upstream release:
- Fix default X server command set to XMir in 1.15.0.
- Internally merge the [SeatDefaults] and [Seat:*] sections together. The
  previous method meant configuration snippets using a mix of old and new
  naming would not correctly override eachother.
- Use IP address of XDMCP requests to contact X server if available.
  (LP: #1481561)
- Add an option for XDMCP and VNC servers to only listen on one address.
  (LP: #1390808)
- Fix configuration file warnings so they go to the log, not stderr.
- Warn if deprecated options logind-load-seats or xdg-seat are in
  configuration. (LP: #1468057)
- Improve IP addresses in XDMCP log messages.
- Fix typo in dm-tool man page. (LP: #1470587)

 -- Robert Ancell robert.anc...@canonical.com  Wed, 05 Aug 2015
16:53:39 +1200

** Changed in: lightdm (Ubuntu)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Currently LightDM connects to an XDMCP enabled X server using the
  first suitable address in the XDMCP Request packet. However, some
  clients may put a number of addresses in this message and potentially
  they are not all routable. If the address the request message came
  from is in the list we should use that first as that is more likely to
  be a routable address. This also matches the behaviour of GDM which
  ignores the contents of the Request packet anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Currently LightDM connects to an XDMCP enabled X server using the
  first suitable address in the XDMCP Request packet. However, some
  clients may put a number of addresses in this message and potentially
  they are not all routable. If the address the request message came
  from is in the list we should use that first as that is more likely to
  be a routable address. This also matches the behaviour of GDM which
  ignores the contents of the Request packet anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Currently LightDM connects to an XDMCP enabled X server using the
  first suitable address in the XDMCP Request packet. However, some
  clients may put a number of addresses in this message and potentially
  they are not all routable. If the address the request message came
  from is in the list we should use that first as that is more likely to
  be a routable address. This also matches the behaviour of GDM which
  ignores the contents of the Request packet anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/lightdm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481561

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Currently LightDM connects to an XDMCP enabled X server using the
  first suitable address in the XDMCP Request packet. However, some
  clients may put a number of addresses in this message and potentially
  they are not all routable. If the address the request message came
  from is in the list we should use that first as that is more likely to
  be a routable address. This also matches the behaviour of GDM which
  ignores the contents of the Request packet anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions

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