AFSlog in OSX 10.3

[Olle Mulmo]

As you discovered, adding the external IP of your NAT apparatus usually
does the trick. I simply added some trivial scripting to fix this problem
myself, but I'm curious as well: why the need for an IP? Can this
limitation / sanity check go away, or at least be made configurable?

/O

-----Original Message-----
From: owner-arla-drinkers at stacken.kth.se
[mailto:owner-arla-drinkers at stacken.kth.se]On Behalf Of Thomas Jordan
Sent: Thursday, October 30, 2003 6:29 PM
To: arla-drinkers at stacken.kth.se
Subject: AFSlog in OSX 10.3


Hello,

I recently reported broken authentication in Arla 0.35.11 and OSX 10.3, 
launching /usr/arla/bin/Afslog.app yielded no tickets, but doing so in 
10.2.8 did.

The authentication in /usr/arla/bin/Afslog.app is fine. I was surprised 
by the switch of kinit's defaults in the move to 10.3 Kinit moved from 
default addressed tickets to addressless ones in the move. 
/usr/arla/bin/Afslog.app works in 10.3 when the tickets have addresses.

This does raise the question of what happens when I am behind NAT and 
am forced to use adressless tickets. Is this an open issue?

Best regards,
	Tom

--
Thomas Jordan
Fermi National Accelerator Lab
PO Box 500 MS 226
Kirk and Pine Streets
Batavia, Illinois
60510
voice: 630.840.4035
fax: 630.840.8248