Hum,
Perhaps I am wrong, but up to you convince me from the opposite the communication does need the server public key (I am missing)
Server Side
- needs the pub key of the client to verify the client
Client Side
- needs the pub key of the server (!!) to verify the server
- needs its own secret key to encrypt the message
So I am missing the definition of the server pub key in the syncbackpro config!
For info the same session works in the discribed way when using the tunnelier bitvise SSH client
Sincerely,
Louis
Perhaps I am wrong, but up to you convince me from the opposite the communication does need the server public key (I am missing)
Server Side
- needs the pub key of the client to verify the client
Client Side
- needs the pub key of the server (!!) to verify the server
- needs its own secret key to encrypt the message
So I am missing the definition of the server pub key in the syncbackpro config!
For info the same session works in the discribed way when using the tunnelier bitvise SSH client
Sincerely,
Louis