>> I just enabled X-forwarding and I've got a few questions for you guys. >> >> Should I have any security concerns about doing this? > > Not more than usual. I assume your online computers have been secured > (to a reasonable degree)... Of course if anyone has access to your > remote machine (that you run X apps on) they could theoretically > "listen" in on your X session (man xauth for details).
Alright, I won't leave remote gimp open all day then. >> It looks like gimp comes through with an older/blockier version of gtk >> or something. Any way to fix that? > > Well, gimp is using local resources on the machine you run it on. So > it's using whatever version of gtk that is installed on your remote > machine. Is it the fonts that are "blocky"? If so it may be an DPI issue ... That's the weird part. Local gimp and remote gimp side-by-side on the same screen look different. For example, the edges of the buttons and widgets in local gimp are rounded but they aren't in remote gimp. Not a big deal though. >> I'm starting X-forwarding like 'ssh -XC 192.168.100.1 gimp' and when I >> close gimp it looks like the terminal is still running the process. >> Is it supposed to come back to the prompt? > > Hm... yes, if you are starting gimp that way it may be that ssh doesn't > recognise that gimp is closed so it maintains the connection. Have you > tried to log in with ssh -X and run it from there instead? When I ssh -X, start gimp, close gimp, and close the ssh session, the terminal prompt disappears and only the cursor is visible in the terminal. I have to ctrl+c to bring the prompt back. This doesn't happen with ssh -X unless I open gimp during the session. > Btw, the -C option is unnecessary unless you are using a very slow connection. Using -C, gimp is about 10x more responsive than if I don't. I was surprised too. My laptop and the "remote" system are 15 feet away from each other on the same wireless network, with the router in between. - Grant
