1/2: Workaround for assumption that WM_STATE atom exists in XIM (possibly the cause of [1])
2/2: With the change to XCSECURITY extension being disabled by default, this has exposed a problem that the code for using authorization cookies for internal clients was condiitonal on that. In fact we should always be using an authorization cookie for internal clients so assure that they can connect in XDMCP sessions (where localhost access to the server may not be permitted). (I think this is the underlying issue in [2]) [1] http://sourceware.org/ml/cygwin-xfree/2008-12/msg00028.html [2] http://sourceware.org/ml/cygwin-xfree/2009-03/msg00008.html Jon TURNEY (2): Cygwin/X: Always use an authorization cookie for internal clients Cygwin/X: Ensure WM_STATE atom exists in multiwindow mode hw/xwin/InitOutput.c | 2 - hw/xwin/win.h | 3 +- hw/xwin/winauth.c | 103 +++++++++++++++++++++++++++++++++++------- hw/xwin/winclipboardthread.c | 19 +------- hw/xwin/winmultiwindowwm.c | 29 ++++++------ include/os.h | 2 + 6 files changed, 106 insertions(+), 52 deletions(-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
