My question:
> I just converted my 4.0D PK#1 2100 to Enhanced security and am receiving
the
> following message when trying to bring up CDE from my PC"
>
> "can not obtain database info on this terminal"
>
> I am unsure exactly how to set the server up for X Clients now. I am
poking around with the man pages but any help or reference material would be
> appreciated. i will summarize.
I got a few responses which helped point me in the right direction, but none
that hit the nail on the head. I was looking for a "wildcard" method of
allowing remote X displays. I did not want to enter every PC in my network
into the devassign and ttys files. After much poking and prodding, the way I
did it was I made two files, ttyent and devent and fed them to edauth.
ttyent looks like this:
*\:*:t_devname=*\:*:t_login_timeout#0:t_xdisplay:chkent:
devent looks like this:
*\:*:v_type=xdisplay:chkent:
then I piped these to edauth like this:
/usr/tcb/bin/edauth -d t -s < ttyent
/usr/tcb/bin/edauth -d v -s < devent
This made a wildcard entry in /etc/auth/system/devassign.db and
ttys.db for X displays. And yes, I realize the security implications. I
handle that with other methods. edauth gives you easy scripting access to
the devassign and tty databases and /usr/tcb/bin/dxdevices gives a gui front
end to them. My problem was I don't have an X display hooked up to that
machine, so I had to use the manual method to get a remote CDE session up.
Then, in order to bring up root in a CDE session I had to add my PC's name
in /etc/securettys like this:
rogers_pc:0
Enjoy!
Received on Thu Jul 15 1999 - 15:07:25 NZST