On 10Jan2023 18:25, Joe Wulf <joe_wulf@xxxxxxxxx> wrote:
I don't know how to solve the problem but can confirm that I have the
same one. From what I have deducted so far is that sshd in F36 and F37
generates new xauth token and replaces the old one every time new
connection is opened.
An alternative is to use a persistent ssh connection, reusing the X11
token from before.
BTW, an incantation of:
ssh host 'x11-client &'
has some scope for dropping the ssh before the client hooks into X11
(thus keeping things open) _if_ the client closes its own output before
connecting to X11. WHich on reflection would be vanishingly rare, since
then it wouldn't get to report failure to connect :-)
Shouldn't the new xauth setup be just fine, though? THe sequence should
be:
- ssh in
- xauth setup on host end
- x11 client connect, _using that new xauth_
I find the xauth scenario a little unconvincing because of this. I'm not
in a position to try to reproduce things though.
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
