>~ : manos 1:44pm > klog
>Password:
>~ : manos 1:44pm > tokens
>
>Tokens held by the Cache Manager:
>
>User's (AFS ID 30379) tokens for [EMAIL PROTECTED] [Expires Dec 1 15:10]
> --End of list--
>~ : manos 1:44pm > which rlogin
>/usr/ucb/rlogin
>~ : manos 1:44pm > rlogin cn10
>AFS (R) 3.3 Login
>~ : cn10 1:44pm > /usr/ciesin/afs/bin/tokens
>
>Tokens held by the Cache Manager:
>
> --End of list--
>~ : cn10 1:44pm >
>---------------------------------------------------------------------------
>
> Am I missing something here? Am I mistaken as to my thoughts of what
> the purpose of these AFS utilities is? Do others experience this same
> thing? I've checked and re-checked to be sure the AFS versions of those
> binaries are the ones which are running.
Maybe, but the Transarc-provided versions don't do it.
Excerpts from internet.info-afs: 30-Nov-94 Hmm. AFS r-commands, new p..
by Jeff [EMAIL PROTECTED]
> Now, by all means correct me if I am wrong, but isn't the whole
> point of having a kerberized in.rlogind, in.rexecd, rsh, login, and rcp
> that authentication will be passed along? Maybe not the WHOLE point,
> but surely a large one.
Derrick has exactly summarized a situation which causes a lot of trouble at
our site:
"Maybe, but the Transarc-provided versions don't do it."
Just to clarify the example above:
Even if one part (the Transarc version of rlogind) is willing to receive
a token you can't send it by /usr/ucb/rlogin because it does not know
anything about token passing.
As far as I know Transarc does not see any need to provide token passing
for rlogin. Transarc recommends to use rsh instead of rlogin :-(
Werner
--
============================================================================
Werner Baur
Leibniz-Rechenzentrum X.400: S=Baur;OU=lrz;P=lrz-muenchen;A=d400;C=de
Barer Str. 21 RFC822: [EMAIL PROTECTED]
D-80333 Muenchen Tel.: ++49-89-2105-8781
Germany Fax: ++49-89-2809460
============================================================================
