Ssh syntax breake in config file #803

New Issue

Closed

opened 2023-12-28 17:55:14 +00:00 by jfoucry · 2 comments

jfoucry commented 2023-12-28 17:55:14 +00:00

Copy Link

What I'm trying to do and why

Hello,

I just want to try to create a repo for a new machine, using the new syntax for the config file.
To not have to reproduce all the setting (from another configuration), I use

borgmatic config generate --source config.yaml --destination config-new.yaml
I changed the hostname the repository/path and the ssh_commandwith the ssh port.

Tried borgmatic rcreate --encryption repokey-aes-ocb but it failed. I change multiple times the way to indicate the custom port but all my try failed. Even with the help of your support in mastodon.

A friend suggest to put the custom port into ~/.ssh/config. The ssh command work immediately, but borgmatic create still failed.

I reread the documentation and find my issue. The path variable must be ssh://user@remotehost/path-to-repository ???!!! And suddenly borg create works. Great \o/

Steps to reproduce

Simply use in repositories/path the "old" ssh syntax: ssh://user@remotehost:path_to_repo, with semi-colon between host and repo path.

Actual behavior

No response

Expected behavior

No response

Other notes / implementation ideas

Wait! The new syntax break the ssh way to indicate the path. Since I use UNIX (a long long time ago, more than 30 years), the ssh syntax is (and still id) ssh://user@remotehost:path-to-go. With a semi colon between the remote host, and the path.

It's not an important bug and reading the documentation solve it in less than 3 minutes. But it brake an old an know by all the UNIX sysadmin around the world. I think this is a mistake in the change of the new syntax.

Excuse my English, my knowledge is very old :-)

borgmatic version

borgmatic --version 1.8.2

borgmatic installation method

FreeBSD ppkg

Borg version

borg --version borg 1.2.6

Python version

python --version Python 3.9.18

Database version (if applicable)

No response

Operating system and version

FreeBSD 14.0-RELEASE-p3

### What I'm trying to do and why Hello, I just want to try to create a repo for a new machine, using the new syntax for the config file. To not have to reproduce all the setting (from another configuration), I use `borgmatic config generate --source config.yaml --destination config-new.yaml` I changed the hostname the `repository/path` and the `ssh_command`with the ssh port. Tried `borgmatic rcreate --encryption repokey-aes-ocb` but it failed. I change multiple times the way to indicate the custom port but all my try failed. Even with the help of your support in mastodon. A friend suggest to put the custom port into `~/.ssh/config`. The ssh command work immediately, but `borgmatic create` still failed. I reread the documentation and find my issue. The path variable must be `ssh://user@remotehost/path-to-repository` ???!!! And suddenly `borg create` works. Great \o/ ### Steps to reproduce Simply use in repositories/path the "old" ssh syntax: `ssh://user@remotehost:path_to_repo`, with semi-colon between host and repo path. ### Actual behavior _No response_ ### Expected behavior _No response_ ### Other notes / implementation ideas Wait! The new syntax break the `ssh` way to indicate the path. Since I use UNIX (a long long time ago, more than 30 years), the `ssh` syntax is (and still id) `ssh://user@remotehost:path-to-go`. With a semi colon between the remote host, and the path. It's not an important bug and reading the documentation solve it in less than 3 minutes. But it brake an old an know by all the UNIX sysadmin around the world. I think this is a mistake in the change of the new syntax. Excuse my English, my knowledge is very old :-) ### borgmatic version borgmatic --version 1.8.2 ### borgmatic installation method FreeBSD ppkg ### Borg version borg --version borg 1.2.6 ### Python version python --version Python 3.9.18 ### Database version (if applicable) _No response_ ### Operating system and version FreeBSD 14.0-RELEASE-p3

jfoucry changed title from Shh syntax breake in config file to Ssh syntax breake in config file 2023-12-28 17:55:33 +00:00

witten commented 2023-12-28 18:03:10 +00:00

Owner

Copy Link

Thanks for taking the time to file this! Is it possible that you were just combining two different versions of the Borg repository URL syntax? For instance, you say that you expected ssh://user@remotehost:path-to-go to work. However, looking at the Borg documentation on this, I'm not sure that particular syntax is supported. What should work though is the old-style user@remotehost:path-to-go syntax without the ssh:// prefix. If that stopped working, then it would definitely be a bug (even though that syntax is deprecated)!

Thanks for taking the time to file this! Is it possible that you were just combining two different versions of the Borg repository URL syntax? For instance, you say that you expected `ssh://user@remotehost:path-to-go` to work. However, looking at the [Borg documentation](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) on this, I'm not sure that particular syntax is supported. What _should_ work though is the old-style `user@remotehost:path-to-go` syntax without the `ssh://` prefix. If that stopped working, then it would definitely be a bug (even though that syntax is deprecated)!

witten added the

question / support

label 2023-12-28 18:03:17 +00:00

witten commented 2024-01-09 21:54:31 +00:00

Owner

Copy Link

I'm closing this for now, but I'd be happy to continue the discussion and/or reopen if necessary. Thanks!

I'm closing this for now, but I'd be happy to continue the discussion and/or reopen if necessary. Thanks!

witten closed this issue 2024-01-09 21:54:31 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#803

No description provided.