Differences

This shows you the differences between two versions of the page.

--- wiki:advanced:x2gobroker:howitworks [2013/03/28 10:35]
sunweaver [Starting vs. Resuming X2Go Sessions]
+++ wiki:advanced:x2gobroker:howitworks [2013/03/28 10:46] (current)
sunweaver [How does X2Go Session Brokerage Work]
@@ Line 1: / Line 1: @@
-====== How does X2Go Session Brokerage Work ======
+====== How does X2Go Session Brokerage Work? ======
 //Provided by Oleksandr Shneyder, edited by Mike Gabriel//
@@ Line 162: / Line 162: @@
 ==== No Auto-Resuming of Sessions ====
-If X2Go Client is running in broker mode, it will not verify if there are existing sessions on X2Go Server.
+If X2Go Client is running in broker mode, it will not verify if there are existing sessions on the targeted X2Go Server.
-It is the responsibility of the X2Go Session Broker. The X2Go Broker should also suspend sessions before providing session data to client if a session is still/already running.
+Checking for running/suspended sessions is the responsibility of the X2Go Session Broker. The X2Go Session Broker should also suspend sessions before providing session data to X2Go Client if a candidate session is still/already running.
 ==== Providing Auto-Login via SSH Keys ====
@@ Line 196: / Line 196: @@
 </code>
-Providing SSH keys can be increase usability of X2Go in several cases.
+Providing SSH keys for X2Go Server sessions can be another mechanism of increasing usability (i.e. reducing the two authentication steps to one, see above).
 It is highly recommended to transfer SSH keys only over encrypted channels (HTTPS or SSH broker).
-It is also recommended to transfer only temporary keys, which should be removed from ''authorized_keys'' directly after successful authentication to X2Go server.
+It is also recommended to only transfer a temporary key, which gets removed from the X2Go Server immediately after successful authentication against the X2Go server.

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools