Re: vncserver problem - .vnc/xstartup: /bin/sh: bad interpreter: Permission denied

From: R S Prigan (NO-SPAM-TO-rprigan_at_insight.rr.com)
Date: 11/24/05 

Date: Thu, 24 Nov 2005 14:42:13 GMT

Tobias Crefeld wrote:

> R S Prigan meinte:
>
>> ** Does anyone know how I can ssh into susebox as a regular user, start
>> the vncserver as a *regular user,* and then have vncviewer work?!?! **
>
> Do you need to run X at the console of your suse-box?
> If not you could make a X-installation with Xvnc as the X-server. This can
> be done by yast's software installation menu. E.g. you select a standard-
> KDE-installation with a simple VGA-Xserver and afterwards you exchange the
> Xserver against Xvnc.
> At the Debian (terminal)-side you could use vncviewer or under KDE krdc.
> AFAIK it will use TLS/SSL to encrypt the vnc-connection but you should
> check this if it is important for you.
> A disadvantage is that you will loose the whole session once it is
> disconnected. In practise this is no problem as long as you stay in a LAN.
> Overall you will get a graphical terminal-server which can run a lot of
> independent X-sessions: One with KDE, another with GNOME, a third as
> root... just depending of the amount of memory and CPU-power that is
> available on this machine.
>
>
>> I have experimented with some permissions. vncserver will not run if
>> set uid root (don't really want *that* either!). Even tried bash (sh is
>> link to bash) as suid root (sure don't want THAT!). ... Debian has
>> vncserver/viewer as 755, SuSE 555 -- this seems not the matter.
>
> I tried a similar approach but it was not very effective: A script to
> start vncserver via ssh with my own account and afterwards starting a
> vncviewer-session. It works and is secure but didn't look very nice and
> comfortable to use.
> An advantage is that you can always break the session and reconnect later.
>
> Someone gave me this link that discusses several approaches:
> http://www.linuxjournal.com/article.php?sid=5499
>
I actually just want to ensure the convenience of vnc to my main box if the
monitor croaks ... and ssh is just another protection (it's on the lan). I
do want to keep using X on the box itself.

Relevant Pages

  • Re: KDE, VNCServer, XFree86, and FreeBSD 5.2.1
    ... but what I'd really like to do is have vncserver bind to ... >>this kde session so I can remotely take control of the console. ... if there is just a couple of apps on the other box then ssh in ...
    (comp.unix.bsd.freebsd.misc)
  • Re: life without system-config-display
    ... to have it running vncserver loaded when X itself starts. ... console X session visible at all stages of the operation of the machine then ... the vnc module needs to be started when X starts - here we are not talking ... starting the vncserver would presumably allow you to make a remote X session ...
    (Fedora)
  • Re: How to GCC? - Bill Campbell/or anybody
    ... his end of the ssh connection. ... ssh extensions and commonly forward port 23 to localhost on the remote ... This allows me to use any terminal emulator on the Windows machine ... the LAN ip of the 3.2v4.2 system. ...
    (comp.unix.sco.misc)
  • Re: Remote Desktop
    ... the performance of forwarded X session for simple X applications ... the LAN provides at least 2 Mb/s speed. ... more remote locations will most likely impose other bottlenecks and rate ... If you think you would like to try X forwarding, ...
    (comp.os.linux.misc)
  • Re: [kde-linux] Sessions names
    ... ssh 192.168.2.80??? ... You can write a wrapper script that would start ssh to some ip and rename the ... konsole session dynamically. ... dcop call to konsole you need to know the pid of konsole. ...
    (KDE)