A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/08 13:05
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround?rev=1483880143
New Revision: http://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround
Edit Summary:
User : stefanbaur
@@ -13,38 +13,38 @@
# Part that runs in regular SSH session
# check we have an agent socket and
- # check we have an ~/.x2goclient directory
+ # check we have an ~/.x2go directory
if [ -n "$SSH_AUTH_SOCK" ] && \
- [ -d ~/.x2goclient ] ; then
+ [ -d ~/.x2go ] ; then
# touch the output file and set permissions
# (as tight as possible)
- touch ~/.x2goclient/agentsocket
- chmod 600 ~/.x2goclient/agentsocket
- chown $USER
~/.x2goclient/agentsocket
+ touch ~/.x2go/agentsocket
+ chmod 600 ~/.x2go/agentsocket
+ chown $USER ~/.x2go/agentsocket
# write file name of agent socket into file
- echo $SSH_AUTH_SOCK >~/.x2goclient/agentsocket
+ echo $SSH_AUTH_SOCK >~/.x2go/agentsocket
fi
# Part that runs in X2Go session
# check we're on an X2GoServer (x2golistsessions is in path),
# check we have a DISPLAY set, and
# check our client DISPLAY and SSH client IP correspond to
# a running X2Go session and
- # check ~/.x2goclient/agent is a regular file
+ # check ~/.x2go/agent is a regular file
if which x2golistsessions >/dev/null && \
[ -n "$DISPLAY" ] && \
[ -n "$(x2golistsessions | \
awk -F '|' '":"$3 == "'$DISPLAY'" && \
$5 == "R" && \
$8 == "'$(echo $SSH_CLIENT | \
awk '{print $1}')'" { print $3 }')" ] && \
- [ -f ~/.x2goclient/agentsocket ] ; then
+ [
-f ~/.x2go/agentsocket ] ; then
# all checks passed, read content of file
# (might still contain stale agent socket or garbage
- MIGHTBEOURAGENT=$(cat ~/.x2goclient/agentsocket)
+ MIGHTBEOURAGENT=$(cat ~/.x2go/agentsocket)
# check if it corresponds to an existing socket
if [ -S "$MIGHTBEOURAGENT" ]; then
# export path to agent socket
export SSH_AUTH_SOCK=$MIGHTBEOURAGENT
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/08 12:55
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround?rev=1483880113
New Revision: http://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround
Edit Summary:
User : stefanbaur
@@ -4,8 +4,9 @@
However, there is a workaround:
Put this at the end of ''/etc/bash.bashrc'' on your X2Go **Server**:
+
<code>
# --- BEGIN X2Go SSH forwarding workaround ---
@@ -52,9 +53,9 @@
# ---- END X2Go SSH forwarding workaround ----
- </file>
+ </code>
Now, start a **regular** SSH session with Agent Forwarding enabled **first**, and leave that session running in the background.
After that, start X2GoClient and connect to your session.
You should now be able
to use the Agent Forwarding created with your regular SSH session from inside your X2Go session.
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/08 12:55
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: ---
New Revision: http://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround
Edit Summary: created
User : stefanbaur
====== Workaround to use SSH Agent Forwarding in an X2Go Session ======
X2GoClient uses ''libssh'' and thus is unable to forward SSH Agent credentials by default.
However, there is a workaround:
Put this at the end of ''/etc/bash.bashrc'' on your X2Go **Server**:
<code>
# --- BEGIN X2Go SSH forwarding workaround ---
# Part that runs in regular SSH session
# check we have an agent socket and
# check we have an ~/.x2goclient directory
if [ -n "$SSH_AUTH_SOCK" ] && \
[ -d ~/.x2goclient ] ; then
# touch the output file and set permissions
# (as
tight as possible)
touch ~/.x2goclient/agentsocket
chmod 600 ~/.x2goclient/agentsocket
chown $USER ~/.x2goclient/agentsocket
# write file name of agent socket into file
echo $SSH_AUTH_SOCK >~/.x2goclient/agentsocket
fi
# Part that runs in X2Go session
# check we're on an X2GoServer (x2golistsessions is in path),
# check we have a DISPLAY set, and
# check our client DISPLAY and SSH client IP correspond to
# a running X2Go session and
# check ~/.x2goclient/agent is a regular file
if which x2golistsessions >/dev/null && \
[ -n "$DISPLAY" ] && \
[ -n "$(x2golistsessions | \
awk -F '|' '":"$3 == "'$DISPLAY'" && \
$5 == "R" && \
$8 == "'$(echo $SSH_CLIENT | \
awk '{print $1}')'" { print $3 }')" ] && \
[ -f ~/.x2goclient/agentsocket ] ; then
# all checks passed, read content of file
# (might still contain stale agent socket or garbage
MIGHTBEOURAGENT=$(cat ~/.x2goclient/agentsocket)
# check if it corresponds to an existing socket
if [ -S "$MIGHTBEOURAGENT" ]; then
# export path to agent socket
export SSH_AUTH_SOCK=$MIGHTBEOURAGENT
fi
fi
# ---- END X2Go SSH forwarding workaround ----
</file>
Now, start a **regular** SSH session with Agent Forwarding enabled **first**, and leave that session running in the background.
After that, start X2GoClient and connect to your session.
You should now be able to use the Agent Forwarding created with your regular SSH session from inside your X2Go session.
Inherent problems:
- Once you close the SSH session, you will be unable to use the SSH Agent Forwarding for new connections within the X2Go session (existing connections will not be terminated, however).
- If you create a new SSH session to the same server after starting the X2Go session, it will overwrite the setting. Again, existing connections will not be
affected, but new connections will use the SSH Agent Forwarding set by the latest SSH connection you made, and once you close the latest SSH session, connections will fail.
- If you share /home (e.g. via NFS) across different X2Go Servers, this workaround will not work reliably.
There's hope that future versions of X2Go will support SSH Agent Forwarding natively, as a patch to add SSH Agent Forwarding has been submitted to the libssh maintainers in March 2016 - but we will have to wait until that patch makes it into all the major distributions.
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/08 12:44
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto?rev=1483543312
New Revision: http://wiki.x2go.org/doku.php/doc:howto
Edit Summary:
User : stefanbaur
@@ -9,4 +9,5 @@
* [[doc:usage:desktop-sharing|Installing and Configuring X2Go Desktop Sharing (Session Shadowing)]]
* [[doc:installation:x2gobroker|Installing X2Go Session Broker]] - careful, this page seems to mix Perl- and Python-based Broker installation
* [[doc:deployment-stories:wikid| Adding two-factor authentication to X2Go]]
* [[doc:howto:nx-libs-betatesting|Betatesting a newer NX-Libs version from Arctica]]
+ * [[doc:howto:ssh-agent-workaround|Workaround to use SSH Agent Forwarding inside an X2Go session]]
--
This
mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/05 15:50
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483631371
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [X2Go-ThinClientEditon-NextGeneration (TCE-NG, TCE-Live, TCE-New, ...)]
User : stefanbaur
@@ -1,5 +1,5 @@
- ====== X2Go-ThinClientEditon-NextGeneration (TCE-NG, TCE-Live, TCE-New, ...) ======
+ ====== X2Go-ThinClientEditon-Live (TCE-Live, formerly known as TCE-NG) ======
<columns 75% ->
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
</columns>
===== History, Rationale, Outlook =====
--
This
mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/05 15:49
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483631087
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [History, Rationale, Outlook]
User : stefanbaur
@@ -3,16 +3,16 @@
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
</columns>
===== History, Rationale, Outlook =====
- During the time of Debian Wheezy being Debian's stable release, we started developing a new ThinClientEdition (TCE) - one that is based on Debian-Live and thus does no longer rely on NFS. Instead, the entire image is loaded into
the RAM of the ThinClient machine.
+ During the time of Debian Wheezy being Debian's stable release, we started developing a new ThinClientEdition then called TCE-NG - one that is based on Debian-Live and thus does no longer rely on NFS. Instead, the entire image is loaded into the RAM of the ThinClient machine. To avoid confusion, and because it now has left the "NG" state, we call it TCE-Live.
The disadvantage is that your ThinClient now needs at least 1 GB of RAM (see below).
- However, the huge advantage is that there no longer is a need for any high-availibility setup concerning NFS. All you need is an HTTP (HTTPS optional for later stages) or FTP server with a dedicated IP, if you want to use netbooting. It is also possible to deploy the image to the ThinClient's local storage, if present, and have it update in the background. Besides, making changes/updating the NFS-based TCE was rather finicky - with the current TCE, you build and deploy a new image every time
you make a change, and you can test it on a single client without interrupting your production environment. The "local storage" feature can also be used to create a portable version of both X2Go-TCE and X2goClient for Windows, sharing the same configuration, on CD/DVD/USB media.
+ However, the huge advantage is that there no longer is a need for any high-availibility setup concerning NFS. All you need is an HTTP (HTTPS optional for later stages) or FTP server with a dedicated IP, if you want to use netbooting. It is also possible to deploy the image to the ThinClient's local storage, if present, and have it update in the background. Besides, making changes/updating the NFS-based TCE (henceforth referred to as TCE-NFS or TCE-Legacy) was rather finicky - with the current TCE-Live, you build and deploy a new image every time you make a change, and you can test it on a single client without interrupting your production environment. The "local storage" feature can also be used to
create a portable version of both X2Go-TCE and X2goClient for Windows, sharing the same configuration, on CD/DVD/USB media.
- We've also received reports that the old NFS-based TCE wouldn't work with Jessie, or at least it was very hard to get it to work.
- Our current TCE works just fine with Jessie, and we expect it to work in Stretch and hopefully in Buster (Stretch+1) as well.
+ We've also received reports that TCE-NFS wouldn't work with Jessie, or at least it was very hard to get it to work.
+ Our TCE-Live works just fine with Jessie, and we expect it to work in Stretch and hopefully in Buster (Stretch+1) as well.
The one catch is that the live-build package in Debian/the Debian-Live project is currently looking for a new maintainer - so there is a slim chance that live-build might be removed from Debian Buster, especially if no new maintainer steps up and the live-build replacement that is currently in the works (called live-wrapper) contains all the required functionality
of live-build by then.
===== ThinClient prerequisites for all variants =====
* At least 1 GB of RAM //unless// you use non-NTFS local storage, in that case, 512MB or even 256MB might work
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/05 15:44
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483629712
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [X2Go-ThinClientEditon-NextGeneration (TCE-NG, TCE-New)]
User : stefanbaur
@@ -1,5 +1,5 @@
- ====== X2Go-ThinClientEditon-NextGeneration (TCE-NG, TCE-New) ======
+ ====== X2Go-ThinClientEditon-NextGeneration (TCE-NG, TCE-Live, TCE-New, ...) ======
<columns 75% ->
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
</columns>
===== History, Rationale, Outlook =====
--
This mail was generated by
DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/05 15:21
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483629697
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [X2Go-ThinClientEditon (TCE-NG, TCE-New)]
User : stefanbaur
@@ -1,5 +1,5 @@
- ====== X2Go-ThinClientEditon (TCE-NG, TCE-New) ======
+ ====== X2Go-ThinClientEditon-NextGeneration (TCE-NG, TCE-New) ======
<columns 75% ->
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
</columns>
===== History, Rationale, Outlook =====
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/05 15:21
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483487042
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [X2Go-ThinClientEditon (TCE, TCE-NG, TCE-New)]
User : stefanbaur
@@ -1,5 +1,5 @@
- ====== X2Go-ThinClientEditon (TCE, TCE-NG, TCE-New) ======
+ ====== X2Go-ThinClientEditon (TCE-NG, TCE-New) ======
<columns 75% ->
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
</columns>
===== History, Rationale, Outlook =====
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/05 00:48
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:usage:desktop-sharing?rev=1479211267
New Revision: http://wiki.x2go.org/doku.php/doc:usage:desktop-sharing
Edit Summary: [The Server Side]
User : stefanbaur
@@ -18,9 +18,9 @@
<code>
$ x2godesktopsharing
</code>
- After starting the application and some searching, you will find a new icon on your panel. On the top the icon it's blue, and under it is white with a red cross in it. When you right-click on the butten you can activate the desktop sharing there. After activating other people who can login, can access your desktop.
+ After starting the application and some searching, you will find a new icon on your panel. On the top the icon it's
blue, and under it is white with a red cross in it. When you right-click on the button you can activate the desktop sharing there. After activating other people who can login, can access your desktop.
===== Client Side =====
To connect to another user's desktop, use [[doc:usage:x2goclient|X2Go Client]]. For installation instructions refer to the [[download:start|download page]].
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/