Hi, first of all: great work with this service! Thank you for putting all the effort into this!
I'm currently using borgserver to backup from one remote machine. I added a borg-ui service in observe mode to conveniently watch over my backups and extract single files from time to time. Great!
Now I wanted to add another repo to backup from a second machine to borgserver. This worked flawlessly but in borg-ui there is a limitation that only one ssh key can be used for a single remote borg server.
Then I had the idea to use the same SSH key for the second repo on borgserver. This messed things up somewhat because the authorized_keys file borgserver generates then include the same SSH key twice with different path restrictions.
The last entry in authorized_keys wins, making the first repo unaccessible.
Any ideas on how to handle this (if at all)?
Hi, first of all: great work with this service! Thank you for putting all the effort into this!
I'm currently using borgserver to backup from one remote machine. I added a borg-ui service in observe mode to conveniently watch over my backups and extract single files from time to time. Great!
Now I wanted to add another repo to backup from a second machine to borgserver. This worked flawlessly but in borg-ui there is a limitation that only one ssh key can be used for a single remote borg server.
Then I had the idea to use the same SSH key for the second repo on borgserver. This messed things up somewhat because the
authorized_keysfile borgserver generates then include the same SSH key twice with different path restrictions.The last entry in
authorized_keyswins, making the first repo unaccessible.Any ideas on how to handle this (if at all)?