Disabling XDMCP
"Rarback, Harvey" <[email protected]> Fri, 31 Oct 2008 17:41:19 -0700
| Newsgroups | gmane.os.tru64.managers |
|---|---|
| Message-ID | <A34E01EABE96174A81D754F98FC574E804D5D799@exch-mail4.win.slac.stanford.edu> |
Tru64 gurus, I am running 4.0f with Enhanced Security and cde as my login manager. The security people here are requiring me to disable XDMCP. Here is what I have tried so far 1. Adding the resource to /usr/var/X11/xdm/xdm-config: DisplayManager.requestPort: 0 2. Adding the entry to /usr/var/X11/xdm/Xaccess: !* 3. Modifying the line in /sbin/init.d/xlogin: $X_DISPLAY_MANAGER -daemon -udpPort 0 $CONFIG_OPTION The first two options didn't change the XDMCP behavior. The last option didn't allow DHCP access which I need. I don't believe the first two options did anything because there is no xdm process running and there is no xdm-errors or xdm-pid file created. When the remote host makes an XDMCP Query request, the remote sees a popup dialog: "Cannot obtain database information on this terminal" And then a popup with the /etc/issue contents, but no login window. When the remote host makes an XDMCP Broadcast the remote host gets a Chooser box which includes the Tru64 hostname and then the above two popups. How can I eliminate any vestige of an XDMCP server? Many thanks for any insights. --Harvey ---- Harvey Rarback phone: (650)926-3963 Stanford Linear Accelerator Center fax: (650)926-4100 2575 Sand Hill Road home phone: (650)560-9111 Menlo Park, CA 94025 [email protected] http://ssrl.slac.stanford.edu/~rarback "Always tell the truth, that way you don't have to keep track." Pogo