#1782 PR closed: Borg backup: Update for using diffrent ssh port

Labels: enhancement, won't fix / can't fix / obsolete

patlegu opened issue at 2018-04-24 22:55:

File need to be modified to use a different port for a remote borg backup.
BORGBACKUP_PORT=<REMOTE PORT> need to be put in /etc/rear/local.conf

Relax-and-Recover (ReaR) Pull Request Template

Please fill in the following items before submitting a new pull request:

Pull Request Details:

  • Type: Bug Fix / New Feature / Enhancement / Other?
    Enhancement

  • Impact: Low / Normal / High / Critical / Urgent
    Low

  • Reference to related issue (URL):

  • How was this pull request tested?
    On a new server with new installation and success of "rear mkbackup"

  • Brief description of the changes in this pull request:
    I'm using a remote borg server with limited borg access (no deletion in repository), limited by the authorized_keys.
    command="borg serve --append-only --restrict-to-path /backup/rear_test" ssh-ed25519 <CLIENT KEY>
    the borg server process is launch when the user connect on the server.

jsmeix commented at 2018-04-25 07:09:

@patlegu see also
https://github.com/rear/rear/pull/1759#issuecomment-374579400
and the subsequent comments therein.

jsmeix commented at 2018-04-26 06:56:

Superseded by https://github.com/rear/rear/pull/1785

[Export of Github issue for rear/rear.]