Re: [rdiff-backup-users] Win 2019 to linux doesn't work

[Dominic Raferd]

On Fri, 29 Mar 2019 at 11:57, Harald Hannelius <address@hidden>
wrote:

>
> On Fri, 29 Mar 2019, Dominic Raferd wrote:
> > On Fri, 29 Mar 2019 at 11:47, Harald Hannelius <
> address@hidden>
> > wrote:
> >> On Fri, 29 Mar 2019, Dominic Raferd wrote:
> >>> On Fri, 29 Mar 2019 at 11:01, Harald Hannelius <
> >> address@hidden>
> >>> wrote:
> >>>
> >>>> If I run the command "ssh -C address@hidden rdiff-backup --server"
> >> I
> >>>> get a rdiff-backup in servermode on the linuxbox and typing characters
> >>>> results in an python-error (which is expected).
> >>>>
> >>>
> >>> I think you haven't specified the key correctly. Here is an example
> using
> >>> plink.exe (from
> >>> https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html):
> >>> rdiff-backup.exe --remote-schema "plink.exe -P 22 -ssh -i
> >>> ""C:\path\to\privatekey.ppk"" %s rdiff-backup --server"
> >>> C:/path/to/SourceData address@hidden::"/backup/repo1"
> >>
> >> Nope, adding the -i option to ssh.exe didn't change anything. If I
> >> copy-the
> >> command in the error-message and run it by itself it works. Same with or
> >> without -i <key>.
> >>
> >
> > Use plink, this is required when connecting from Windows.
>
> I tried that too. I have the plink.exe command that starts a remote
> rdiff-backup on the linux-server and it works from the commandline on the
> windows-server.
>
> However, rdiff-backup is unable to use plink.exe and fails with the same
> error.
>

Googling the error shows that it has been seen with connection from Linux
clients, so I don't think it relates to Windows. Are you confident that you
have the same versions of rdiff-backup on client and on server? Otherwise I
am out of ideas (I don't have Windows 2019 Server).