On Fri, 2007-09-28 at 14:27 +0100, Bill Crawford wrote:
On 27/09/2007, Adam Jackson <ajackson(a)redhat.com> wrote:
> Why is this not a bug in kerberos? If the application knows that the IP
> address it wants for the name needs to be globally routable, then the
> application should be responsible for walking the list of IPs for that
> name to find the routable ones.
Another point being missed, is that if the hostname gets changed the
moment an external IP interface is brought up, X becomes unusable
because suddenly the magic cookie isn't found (the server and
.Xauthority think it's "localhost" and the client thinks it's
"some-dynamic-ip-xx-yy-zz.imaginative-dsl-provider.com").
I think there's something more subtle going on in this case. What we do
at least in startx(1) is add the cookie to ~/.Xauthority twice, once
for :0 and once for foo:0, so the first one should always win.
- ajax