good evening all xmove, the screen for x app, seems to really hate the ssh "it just works" philosophy. i am trying to display xmove'd applications onto a remote system through ssh tunneling.
"xmove is not authorized to connect to server localhost:10." localhost:10 being a ssh x forwarding tunnel which works fine for everything else i've ever done on it. so basically it looks something like this. xmove is a proxy x application. someplace along the line of connecting to the x server, it fails to xauth itself properly. even an xhost + on every side involved is insufficient to fix the problem. xmove really hates ssh, with a passion, which is a pity because they go together like bread and butter. it was my hope that i could just export a magic cookie from my remote host, and import it with a different display name into my .Xauthority. my remote host exports a cookie for remotehost:0. I was hoping i could find something in xauth which would let me take this extracted xauth magic-cookie and transmogify it to a localhost:10 magic-cookie. unfortunately i've been unable to man or google anything suitable for the task. i dont even know if this general plan of attack would work in getting xmove working, i dont know if xauth is designed to work under such hackery, but i have a feeling that if ssh forwarded raw x frames and i gave xmove the right end of the tunnel (localhost:10) and the right xauthority, it could bypass whatever dance ssh and xmove's xauth client clusterfsck each other on. if anyone has suggestions and or a saner plan of attacks, the world at large would be very much oblidged. this issue was brought up before. http://lists.debian.org/debian-user/2004/01/msg02872.html please help myren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
