| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management) Resent-To: krb5-unassigned@RT-11.MIT.EDU Resent-Reply-To: krb5-bugs@MIT.EDU, benjid@teamnet.net Date: Wed, 15 Oct 1997 13:54:43 -0500 (CDT) From: benjid@teamnet.net Reply-To: benjid@teamnet.net To: krb5-bugs@MIT.EDU >Number: 480 >Category: krb5-clients >Synopsis: how to enable kerberos authentication with XDM >Confidential: no >Severity: non-critical >Priority: low >Responsible: krb5-unassigned >State: open >Class: support >Submitter-Id: unknown >Arrival-Date: Wed Oct 15 14:55:00 EDT 1997 >Last-Modified: >Originator: Ben Dehner >Organization: Team Technologies Cedar Falls, IA >Release: 1.0pl1 >Environment: System: IRIX media 6.2 03131015 IP22 network of IRIX systems >Description: I have set up and installed Kerberos V at our site; all clients and servers work as expected. However, many people use X-clients (X terminals or X software on a PC) to log in to servers, which bypasses Kerberos authentication. Is there a way to force the X display manager (xdm) to use Kerberos authentication instead of normal Unix password file authentication? I have tried replacing the "login" program with the Kerberos login.krb5, but apparently the xdm uses its own internal authentication instead of going through "login". >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted:
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |