upstream/borgbackup
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2026-03-04 14:30:32 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

docs: borg-serve: simplify example of env in authorized_keys

Browse source 
see #8318

so long as it can be assumed that the user has configured a POSIX
compliant login shell, using a simple command [1] looks cleaner, as
no ``export`` or ``;`` are used.

[1] Section "2.9.1 Simple Commands" in volume "Shell & Utilities" of POSIX.1-2024
This commit is contained in:
Max-Julian Pogner 2025-01-04 01:09:33 +01:00 committed by Thomas Waldmann
parent 391248da6c
commit c77f005307
No known key found for this signature in database
GPG key ID: 243ACFA951F78E01
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/usage/serve.rst
View file

@ -29,10 +29,12 @@ locations like ``/etc/environment`` or in the forced command itself (example bel
# Set a BORG_XXX environment variable on the "borg serve" side
$ cat ~/.ssh/authorized_keys
command="export BORG_XXX=value; borg serve [...]",restrict ssh-rsa [...]
command="BORG_XXX=value borg serve [...]",restrict ssh-rsa [...]
.. note::
The examples above use the ``restrict`` directive. This does automatically
The examples above use the ``restrict`` directive and assumes 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.