HP Workstation zx6000 HP Graphics Administration Guide for HP-UX 11.X (IPF ver - Page 40

connecting to the network, granting access, property XDCCC_LINEAR_RGB_CORRECTION

Page 40 highlights

configuring an X Server on HP-UX property RGB_BLUE_MAP property RGB_GRAY_MAP root ar root ar # To let untrusted clients use the color management database # created by xcmsdb, include these lines. property XDCCC_LINEAR_RGB_CORRECTION root ar property XDCCC_LINEAR_RGB_MATRICES root ar property XDCCC_GRAY_SCREENWHITEPOINT root ar property XDCCC_GRAY_CORRECTION root ar # To let untrusted clients use the overlay visuals that many # vendors support, include this line. property SERVER_OVERLAY_VISUALSroot ar # 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". Reads and writes will cause an # error. property Woo-Hoo OhBoy = "*son"ad 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 Graphics Administration Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66

4–28
Graphics Administration Guide
configuring an X Server on HP-UX
property RGB_BLUE_MAP
root
ar
property RGB_GRAY_MAP
root
ar
# To let untrusted clients use the color management database
# created by xcmsdb, include these lines.
property XDCCC_LINEAR_RGB_CORRECTION
root
ar
property XDCCC_LINEAR_RGB_MATRICES
root
ar
property XDCCC_GRAY_SCREENWHITEPOINT
root
ar
property XDCCC_GRAY_CORRECTION
root
ar
# To let untrusted clients use the overlay visuals that many
# vendors support, include this line.
property SERVER_OVERLAY_VISUALSroot
ar
# 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”.
Reads and writes will cause an
# error.
property Woo-Hoo
OhBoy = “*son”ad
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.