|
@@ -29,13 +29,14 @@ locations like ``/etc/environment`` or in the forced command itself (example bel
|
|
|
|
|
|
# Set a BORG_XXX environment variable on the "borg serve" side
|
|
# Set a BORG_XXX environment variable on the "borg serve" side
|
|
$ cat ~/.ssh/authorized_keys
|
|
$ cat ~/.ssh/authorized_keys
|
|
- command="export BORG_XXX=value; borg serve [...]",restrict ssh-rsa [...]
|
|
|
|
|
|
+ command="BORG_XXX=value borg serve [...]",restrict ssh-rsa [...]
|
|
|
|
|
|
.. note::
|
|
.. note::
|
|
- The examples above use the ``restrict`` directive. This does automatically
|
|
|
|
- block potential dangerous ssh features, even when they are added in a future
|
|
|
|
- update. Thus, this option should be preferred.
|
|
|
|
-
|
|
|
|
|
|
+ The examples above use the ``restrict`` directive and assume a POSIX
|
|
|
|
+ compliant shell set as the user's login shell.
|
|
|
|
+ This does automatically block potential dangerous ssh features, even when
|
|
|
|
+ they are added in a future update. Thus, this option should be preferred.
|
|
|
|
+
|
|
If you're using openssh-server < 7.2, however, you have to explicitly specify
|
|
If you're using openssh-server < 7.2, however, you have to explicitly specify
|
|
the ssh features to restrict and cannot simply use the restrict option as it
|
|
the ssh features to restrict and cannot simply use the restrict option as it
|
|
has been introduced in v7.2. We recommend to use
|
|
has been introduced in v7.2. We recommend to use
|