Re: recent openssh lossage
Ar an seachtú lá de mí Eanair, scríobh Jamie Zawinski:
So what would be nice would be if xemacs would notice that it was
failing because of the "Security" extension and provide a better error
message than "no selection" (or whatever it says now.)
That could be done by calling XListExtensions, and checking for an entry for
the SECURITY extension. If it exists, we don’t have the problem. If it
doesn’t, we’re either an untrusted client, or the server doesn’t have the
extension; if we’re particularly energetic, we can check this latter using
the “new authorization method” described in the spec, to make a separate,
unauthenticated, connection to the X server which will succeed if the
Security extension is available.
There’s apparently, intentionally, no explicit way of working out directly
that an XGetProperty request failed because the X server thinks we’re an
untrusted client.
Perhaps there's some way to tell the security extension that
"yes,
selection transfers should still be allowed anyway"? I can't make much
sense of it, but the protocol spec seems to be hinting that such things
are possible?
Yeah, it refers readers to the Xserver manual page and the -sp option, for a
security policy file, which could be changed to allow XGetProperty to
work. I expect the OS distributors will do that right about when the US goes
metric.
--
“Ah come on now Ted, a Volkswagen with a mind of its own, driving all over
the place and going mad, if that’s not scary I don’t know what is.”