Connecting To The Network; Granting Access - HP zx2000 Supplementary Manual

configuring an X Server on HP-UX
property RGB_BLUE_MAP
property RGB_GRAY_MAP
# To let untrusted clients use the color management database
# created by xcmsdb, include these lines.
property XDCCC_LINEAR_RGB_CORRECTION
property XDCCC_LINEAR_RGB_MATRICES
property XDCCC_GRAY_SCREENWHITEPOINT
property XDCCC_GRAY_CORRECTION
# To let untrusted clients use the overlay visuals that many
# vendors support, include this line.
property SERVER_OVERLAY_VISUALSroot
# Oddball property names and explicit specification of error
# conditions.
property "property with spaces" 'property with "'aw er ed
# Allow deletion of Woo-Hoo if window also has property OhBoy
# with value ending in "son".
# error.
property Woo-Hoo

connecting to the network

The X Server supports client connections via a platform-dependent subset of the following
transport types: TCP/IP and UNIX Domain sockets.

granting access

This section comes directly from the XFree86 Xserver(1) manual page.
The X Server implements a platform-dependent subset of the following authorization protocols:
MIT-MAGIC-COOKIE-1, XDM-AUTHORIZATION-1, SUN-DES-1, and MIT-KERBEROS-5.
See the Xsecurity(1) manual page for information on the operation of these protocols.
Authorization data required by the above protocols is passed to the server in a private file named
with the –auth command line option. Each time the server is about to accept the first
connection after a reset (or when the server is starting), it reads this file. If this file contains any
authorization records, the local host is not automatically allowed access to the server, and only
clients which send one of the authorization records contained in the file in the connection setup
information is allowed access. See the Xau manual page for a description of the binary format of
this file. See xauth(1) for maintenance of this file, and distribution of its contents to remote
hosts.
The X Server also uses a host-based access control list for deciding whether or not to accept
connections from clients on a particular machine. If no other authorization mechanism is being
used, this list initially consists of the host on which the server is running as well as any machines
listed in the file /etc/Xn.hosts, where n is the display number of the server. Each line of the
file should contain either an Internet hostname (e.g. expo.lcs.mit.edu) or a DECnet
hostname in double colon format (e.g. hydra::). There should be no leading or trailing spaces
on any lines.
4–28
root
root
Reads and writes will cause an
OhBoy = "*son"ad
Graphics Administration Guide
ar
ar
root ar
root ar
root ar
root ar
ar