@@ -120,10 +120,16 @@ First of all, verify that your agent is running. You can do this by executing::
120
120
121
121
If the agent is not running, you will get a
122
122
``Could not open a connection to your authentication agent. `` message. In this
123
- case you can start the agent with::
123
+ case you can start an instance of the agent with::
124
124
125
125
eval $(ssh-agent)
126
126
127
+ .. note ::
128
+ If you start your agent in this way, it is only accessible within the context of your
129
+ current shell. If you want to connect with NoMachine NX, you should also start your
130
+ NoMachine client from within this shell via the ``nxplayer `` command. Otherwise it will
131
+ not be able to access the certificate stored in your agent.
132
+
127
133
(to kill the agent use ``eval "$(ssh-agent -k)" ``)
128
134
129
135
If your agent is running, the ``ssh-add -l `` will list the identities that were
@@ -157,10 +163,13 @@ continuing:
157
163
The indentation is not strictly necessary, but is recommended for readability.
158
164
159
165
If you now connect to the cluster using your standard ``ssh `` command, the
160
- certificate will automatically be stored for as long as your agent lives. If
161
- you want to use apps that use ``ssh `` in the background (NX, FileZilla), you will
162
- have to do this connection to the cluster as well. You are free to log out of
163
- that session afterwards.
166
+ certificate will automatically be stored for as long as your agent lives.
167
+
168
+ If you want to use apps that use ``ssh `` in the background (NX, FileZilla), you
169
+ should also first inject a certificate in your agent before trying to connect.
170
+ This can be done by connecting to the VSC firewall page with agent forwarding::
171
+
172
+
164
173
165
174
.. note ::
166
175
0 commit comments