[1573] in Kerberos_V5_Development
Re: telnetd
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Wed Aug 14 12:37:29 1996
Date: Wed, 14 Aug 1996 12:36:52 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: hartmans@MIT.EDU
Cc: krbcore@MIT.EDU
In-Reply-To: <199608140031.UAA20409@tertius.mit.edu> (message from Sam Hartman
on Tue, 13 Aug 1996 20:31:56 -0400)
OK, the telnetd in the krb5 locker build tree does in fact
work with Kerberos 5 authentication and encryption.
Well, I tried again using exactly the same binaries today, and it
worked. I guess I was just confused.
I am still confused, however, about the -a option. Here is what I
just determined empirically:
-a user, -a valid: identical behavior, both require krb5 autht, both
use .k5login authz.
-a none, -a off: both perform krb5 authentication if provided but do
not require it, and both use /bin/login for password authentication.
This is not what the man page says, and it seems odd that these
behaviors are in fact identical. Can someone explain what is really
happening?
Barry
