Written by Aninhumer the 2 Jun 09 at 16:24.

I am not at all familiar with these protocols, but I think SIP is most likely to be the most sensible, as it is the Session Initiation Protocol.
I presume there is a way to use SIP to initiate an SSH connection, bypassing routers and firewalls, from one user to another.
This could also include a special user, given sudo privileges and a random password to encourage the use of sudo (although obviously they could acquire root access easily)
There would then be a plugin for a messaging client giving the option to offer or request ssh access to another user.

There are obviously many many security issues with this kind of thing so it should definitely be optional, and have appropriate warning messages throughout, especially about not allowing people you don't know to use it.
Various limitations could be put in place to help prevent abuse, such as only allowing the user to run certain programs (apt-get etc.) as root.
The session shell could also be shown to the user being assisted, so even inexperienced users can see if a suspicious output or command appears, allowing them to pause the session and question their helper about it, and end the session if they are not happy.

(I put Pidgin as the related Project as it is the default IM client in Ubuntu, but obviously any messaging client could be used)

I am not at all familiar with these protocols, but I think SIP is most likely to be the most sensible, as it is the Session Initiation Protocol. I presume there is a way to use SIP to initiate an SSH connection, bypassing routers and firewalls, from one user to another. This could also include a special user, given sudo privileges and a random password to encourage the use of sudo (although obviously they could acquire root access easily) There would then be a plugin for a messaging client giving the option to offer or request ssh access to another user. There are obviously many many security issues with this kind of thing so it should definitely be optional, and have appropriate warning messages throughout, especially about not allowing people you don't know to use it. Various limitations could be put in place to help prevent abuse, such as only allowing the user to run certain programs (apt-get etc.) as root. The session shell could also be shown to the user being assisted, so even inexperienced users can see if a suspicious output or command appears, allowing them to pause the session and question their helper about it, and end the session if they are not happy. (I put Pidgin as the related Project as it is the default IM client in Ubuntu, but obviously any messaging client could be used)

Written by cheesehead the 2 Jun 09 at 16:53.

An easy and already-existing way to offer desktop support is a reverse VNC connection.

In this setup, the user gets the helper on the phone, and then clicks one icon to initiate the connection. That's all they do. No server on the user's computer, no user permissions issues, no users fiddling with router ports or IP addresses or SSH tunnels - all those technical details of the connection are at the helper's end.

I use them regularly, and they work great.
A very good guide is at http://ubuntuforums.org/showthread.php?t=299489

An easy and already-existing way to offer desktop support is a reverse VNC connection. In this setup, the user gets the helper on the phone, and then clicks one icon to initiate the connection. That's all they do. No server on the user's computer, no user permissions issues, no users fiddling with router ports or IP addresses or SSH tunnels - all those technical details of the connection are at the helper's end. I use them regularly, and they work great. A very good guide is at http://ubuntuforums.org/showthread.php?t=299489

Written by P4man the 18 Jun 09 at 07:46.

Crossloop is *exactly* what ubuntu needs. Its idiot proof, seems secure, allows commercial or free support from friends or strangers, and its a lot faster than the built in vinoserver which is agonizingly slow (even on a 100Mbit LAN).

crossloop is based on tightvnc, and currently available for windows and OS-X. Lets try and convince them to port it to ubuntu, it should be easy given what its based upon and should be win-win for crossloop marketplace and for ubuntu. This is the sort of app that should be bundled with ubuntu by default to help out all the new users.

Alternative: build a clone that works in a similar way, without needing to set up portforwarding, reverse ssh or anything a total newbie can't be expected to figure out. Just click an icon and ask someone for help.

Crossloop is *exactly* what ubuntu needs. Its idiot proof, seems secure, allows commercial or free support from friends or strangers, and its a lot faster than the built in vinoserver which is agonizingly slow (even on a 100Mbit LAN). crossloop is based on tightvnc, and currently available for windows and OS-X. Lets try and convince them to port it to ubuntu, it should be easy given what its based upon and should be win-win for crossloop marketplace and for ubuntu. This is the sort of app that should be bundled with ubuntu by default to help out all the new users. Alternative: build a clone that works in a similar way, without needing to set up portforwarding, reverse ssh or anything a total newbie can't be expected to figure out. Just click an icon and ask someone for help.

Written by Sauerkraut the 23 Oct 09 at 13:06.

An on-line-platform should be created. There, users can connect with their friends, find peers who help them or find commercial support (eg. from Canonical).

A user who needs help needs to install a small client via the software-center. When started, the client connects to the platform and allows the user to grant (temporarily) their friends, peers or whoever, the necessary rights to access their pc.

The user who helps, uses the same client-application. The application allows him to establish an ssh- or vnc-connection. If no direct connection is possible, the connection is routed via the on-line-platform.

An on-line-platform should be created. There, users can connect with their friends, find peers who help them or find commercial support (eg. from Canonical). A user who needs help needs to install a small client via the software-center. When started, the client connects to the platform and allows the user to grant (temporarily) their friends, peers or whoever, the necessary rights to access their pc. The user who helps, uses the same client-application. The application allows him to establish an ssh- or vnc-connection. If no direct connection is possible, the connection is routed via the on-line-platform.

Written by johann-1.0 the 21 Aug 10 at 10:24.

Make clones of these softwares so it be easy for Ubuntu users to install it via Synaptic and give remote assistance to less experienced users. This will help promote switching to Ubuntu.
A user who needs help and the helper both install this package. They forget about configuration, router, etc. They only connect through this software.
Also, it doesn't matter any possible combinations, this means:

Helper one----Helped one
Windows-------Linux
Linux---------Windows
Windows.----..Mac
Mac..------...Windows
Linux..-----..Mac
Mac-----------Linux

Make clones of these softwares so it be easy for Ubuntu users to install it via Synaptic and give remote assistance to less experienced users. This will help promote switching to Ubuntu. A user who needs help and the helper both install this package. They forget about configuration, router, etc. They only connect through this software. Also, it doesn't matter any possible combinations, this means: Helper one----Helped one Windows-------Linux Linux---------Windows Windows.----..Mac Mac..------...Windows Linux..-----..Mac Mac-----------Linux

Written by OerHeks the 11 Jul 12 at 21:54.

Please evaluate this support idea,

"Allow remote acces to your desktop by a Voluteer"

Volunteer will have a seperate mousepointer, or even a different type of pointer, to Guide you trough the Solution steps provided by the Volunteer or Wiki documentation.
The Volunteer has no acces to push a button or acces the commandline, just a 'Guiding-pointer'

Key is doing it yourself."

In short, a remote desktop service, where the client has got a second mousepointer to guide the user trough the steps of the solution, arrowing to the places the user needs to be.

Please evaluate this support idea, "Allow remote acces to your desktop by a Voluteer" Volunteer will have a seperate mousepointer, or even a different type of pointer, to Guide you trough the Solution steps provided by the Volunteer or Wiki documentation. The Volunteer has no acces to push a button or acces the commandline, just a 'Guiding-pointer' Key is doing it yourself." In short, a remote desktop service, where the client has got a second mousepointer to guide the user trough the steps of the solution, arrowing to the places the user needs to be.