From a497d73b93a9a60cdfedc8aeb3536ded7a19f35f Mon Sep 17 00:00:00 2001 From: "a@92214b2eae95307f511e06845d2cb5b5931b00a3" Date: Fri, 10 Feb 2023 17:08:32 +0000 Subject: [PATCH] --- ...nect_to_newly_added_remote_on_Windows.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/bugs/Fails_to_connect_to_newly_added_remote_on_Windows.mdwn diff --git a/doc/bugs/Fails_to_connect_to_newly_added_remote_on_Windows.mdwn b/doc/bugs/Fails_to_connect_to_newly_added_remote_on_Windows.mdwn new file mode 100644 index 0000000000..3f6a1320e3 --- /dev/null +++ b/doc/bugs/Fails_to_connect_to_newly_added_remote_on_Windows.mdwn @@ -0,0 +1,22 @@ +### Please describe the problem. + +After adding a new SSH remote with the assistant on Windows, git-annex can't connect the remote. + +### What steps will reproduce the problem? + +1. On Windows, add a new "Remote server" repository in the webapp. +2. Use password authentication. The pairing will succeed initially but it will be added as a "metadata only" remote because SSH connections using the new key pair fail. + +### What version of git-annex are you using? On what operating system? + +git-annex 10.20221213-gac824ff96 + +Installed with the scoop package on Windows. + +### Please provide any additional information below. + +The problem seems to be that the private key is written with CRLF line endings. I can manually SSH to the remote (using git-annex's key) with the system-installed `ssh`, but Git for Windows rejects the key as invalid until it's converted to LF line endings. + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +Yes! I've been using git-annex from the command line to manage my music library for years. Now I'm in the middle of replacing my Syncthing usage with git-annex assistant.