Skip to content
Snippets Groups Projects

Use restrict key option and relative borg command

Merged Evangelos Foutras requested to merge simplify-borg_client-authorized_keys into master

No functional change; the "restrict" key option is a shorthand for:

  • no-agent-forwarding
  • no-port-forwarding
  • no-X11-forwarding
  • no-pty
  • no-user-rc

It was added in OpenSSH 7.2 (2016-02-29) as a convenient way to specify an authorized key should have "all current and future key restrictions" applied to it.

Also switch to a relative borg command since its location is not really standardized; on rsync.net it appears to be located under usr/local/bin (though /usr/bin/borg works too, even if it doesn't exist!) and Hetzner just forces its own command, ignoring ours. :cat:

The Borg documentation seems to agree with both the above alterations:

[1] https://borgbackup.readthedocs.io/en/stable/usage/serve.html

Merge request reports

Pipeline #9150 passed

Pipeline passed for 3561a383 on simplify-borg_client-authorized_keys

Approved by
Ready to merge by members who can write to the target branch.

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
Please register or sign in to reply
Loading