File: Fails_to_connect_to_newly_added_remote_on_Windows.mdwn

package info (click to toggle)
git-annex 10.20250721-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 74,484 kB
  • sloc: haskell: 90,982; javascript: 9,103; sh: 1,469; makefile: 213; perl: 137; ansic: 44
file content (22 lines) | stat: -rw-r--r-- 1,198 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
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.