[4901] in Kerberos
Re: terminal server questions
daemon@ATHENA.MIT.EDU (Dean Guenther - Systems Staff)
Fri Mar 31 21:08:22 1995
To: kerberos@MIT.EDU
Date: Fri, 31 Mar 1995 22:48:57 GMT
From: guenther@unicorn.it.wsu.edu (Dean Guenther - Systems Staff)
Stephen, we are using Xyplex terminal servers. Whereas they are doing very well
with authentication, (and other nifty features the network folks like) there is
a severe limitation (IMHO). They only allow a max of a 16 character principal.
This seems too restrictive to me. Digital's DS700 terminal server allows up
to 40 characters. I doubt we'll switch from Xyplex. I'm hoping instead that
Xyplex will change their minds about their implementation of principal length.
In article <1995Mar24.170446.22381@cti.wnc.nedlloyd.nl>, stephen@zeus.wnc.nedlloyd.nl (Stephen Tittel) writes:
|> I have the following problem. I'm doing research for the possibilities
|> to implement Kerberos in our corporate network. The network is built up
|> with only terminals, connect via terminal servers to the LAN to work
|> with the provided applications on the computersystems. Users don't have
|> a workstation to work on.
|>
|> Furthermore, the users of remote offices are connected via only a terminal,
|> the terminal server and the WAN to use the applications in our computer
|> centre. The terminal server isn't managed by our company on account of
|> boarding out.
|>
|> In general, how do people solve authentication of users working only with
|> a terminal? Is it possible that a PC connected with the terminal server
|> handles all the Kerberos request between the terminal and the Kerberos
|> server?
|>
|> Stephen
|> --------------------------------------------
|> stephen@cti.wnc.nedlloyd.nl
|> Network & Security
|> Nedlloyd Computer Services B.V.
|> Rotterdam, Holland
|>
--
Dean Guenther Internet: guenther@wsu.edu
Washington State University AT&T: 509 335-0433
Pullman, WA. 99164-1222 fax: 509 335-0540
