Wildcarding C2 ttys/devassign entries

From: Simon Greaves <Simon.Greaves_at_usp.ac.fj>
Date: Fri, 19 Mar 1999 16:38:51 +1200

I have a number of PC's with eXcursion X server software. I have been
asked to provide XDMCP access to our [DT]U servers. From the archive I
picked up an article describing how to create wildcard
/etc/auth/system/ttys and /etc/auth/system/devassign entries. Which
works ok, but since that matches against any host, what I really wanted
to do was to widcard given subnets.

The following works:

        /tcb/bin/edauth -dt -s <<-\X
        *\:*:\
                :t_devname=*\:*:t_lock_at_:t_login_timeout#0:t_xdisplay:\
                :chkent:
        X
        /tcb/bin/edauth -dv -s <<-\X
        *\:*:\
                :v_devs=*\:*:v_type=xdisplay:chkent:
        X

Leaving the devassign entry as it is, I tried to use a more restrictive
ttys wildcard:

        /tcb/bin/edauth -dt -s <<-\X
        nnn.mmm.*\:*:\
              :t_devname=nnn.mmm.*\:*:t_lock_at_:t_login_timeout#0:\
              :t_xdisplay:chkent:
        X

which edauth seems to accept, but then I get the notorious "Cannot
obtain database info" dialog.

I also tried:

        /tcb/bin/edauth -dt -s <<-\X
        nnn.mmm.*\:*:\
              :t_devname=*\:*:t_lock_at_:t_login_timeout#0:\
              :t_xdisplay:chkent:
        X

Which edauth rejected.

I tried using Xaccess to restrict the hosts that could get a chooser,
but this only seems to work on hostnames and the PC's are not DNS
registered. I think it would be impractical to manage a hostname/IP
address list.

Any suggestions? (Am I being overly paranoid?), thanks,

Simon
-- 
Simon Greaves                           voice: (+679) 212114
Computer Centre                         fax:   (+679) 304089
The University of the South Pacific     email: Simon.Greaves_at_usp.ac.fj
Suva, Fiji
Received on Fri Mar 19 1999 - 03:48:52 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:39 NZDT