Date: Wed, 18 Dec 2013 21:08:01 GMT From: Adrian Chadd <adrian@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/184978: dhclient hostname changes can invalidate xauth sessions Message-ID: <201312182108.rBIL81HA099421@oldred.freebsd.org> Resent-Message-ID: <201312182110.rBILA0WJ049553@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 184978 >Category: bin >Synopsis: dhclient hostname changes can invalidate xauth sessions >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 18 21:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Adrian Chadd >Release: -HEAD >Organization: >Environment: N/A - applies to 9.x, 10.x, 11.0 >Description: The hostname (re)setting via dhclient-script seems to cause the whole xauth session to suddenly be invalid. This prevents new X applications from starting. In a world where one can't just restart the X server without rebooting, this is a bit of a problem. >How-To-Repeat: Start an xauth session, then jump on a network whose DHCP server resets the hostname for you. >Fix: Changing the hostname back to the original hostname fixes things. I don't know whether disabling the hostname setup via dhclient is the right thing to do but it seems the only thing that works for me. >Release-Note: >Audit-Trail: >Unformatted:help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312182108.rBIL81HA099421>