[1691] in Kerberos
Re: [jnm@tdum.ctd.ornl.gov (Jamey Maze): Problem with MIT Kerberized "MH"]
daemon@ATHENA.MIT.EDU (Tom Coppeto)
Mon Dec 30 17:55:46 1991
To: jnm@tdum.ctd.ornl.gov
Cc: jon@MIT.EDU (Jon A. Rochlis), kerberos@MIT.EDU
In-Reply-To: Your message of Mon, 30 Dec 91 15:53:55 +0000.
Date: Mon, 30 Dec 91 16:25:35 GMT
From: Tom Coppeto <tom@MIT.EDU>
Here are a couple of things I picked up in your transcript...
- Tom
> tdum% inc -norpop
> Password (gryphon:jnm1):
...
> I'm a bit confused as to why inc prompts for a password.
My first reaction is that it is documented behavior in the man page.
The kerberos integration into mh (given how gross mh is) is probably
not compatible with other "authentication" mechanisms inc supports. We
have one way of using it here and that's with kerberos and no one uses
any of those options.
> inc: -ERR Kerberos authentication failure: Can't decode authenticator (krb_rd_req)
...
> Dec 27 14:33:02 Dec 27 22:33:02 krbtgt.ORNL.GOV@ORNL.GOV
> Dec 27 14:33:10 Dec 27 22:33:10 kpop.gryphon@ORNL.GOV
^^^^
it needs the "pop" key, not "kpop", unless you changed our version of
inc. The key is not related to the service port.
