Closed unxed closed 4 years ago
sounds similar to unsupported encryption schema that resolvable by compiling super-fresh libssh, cannot find issue, but AFAIR @singalen posted it (and resolved) some time ago
Stupid question, but: how to tell far2l prefix of custom openssh build?
not openssh, but libssh
try: cmake -DCMAKE_BUILD_TYPE=Release -DLIBSSH_LIBRARIES=/home/user/projects/libssh/libssh-0.9.0-build/lib/libssh.so -DLIBSSH_INCLUDE_DIRS=/home/user/projects/libssh/libssh-0.9.0/include ../far2l
note that include dirs root differs from libs - it points to sources, while libs points to build results. Be careful with that include path - if you will specify wrong path - it will look into system's include directory and if you have libssh installed there - will use it instead of correct one.
Did
cmake -DCMAKE_BUILD_TYPE=Release -DLIBSSH_LIBRARIES=/home/unxed/far2l/test_libssh/far2l/libssh-0.9.2/build/lib/libssh.so -DLIBSSH_INCLUDE_DIRS=/home/unxed/far2l/test_libssh/far2l/libssh-0.9.2/include ../far2l
Still "key auth failed" :(
Did apt remove libssh-4 libssh-dev
to verify that correct libssh version is used, repeated cmake & make.
Still the same error.
Custom libssh build is used for sure: if I rename the folder with it, sftp broker fails to start.
ok, need logs from netrocks open terminal, type there: export FAR2L_STD=- export NETROCKS_VERBOSE=3 ..and finally run far2l (in GUI mode) from that terminal - it will write much debug logs
Oh, it was entirely my fault :) Closing :))
Instance is running Amazon Linux 2018.03 Console ssh client connects ok with the same keyfile. Console ssh client log (don't know how to get logs from netrocks):