Hello Mark,
thank you for pointing me out to this problem. I do understand that due
to the aforementioned vulnerability Guile-SSH cannot do its job well.
So I'll port Guile-SSH to libssh 0.6.3 where the vulnerability was
closed. I think this solution is acceptable.
- Artyom
--
Artyom Poptsov
Hi.
> Upgrading libssh from 0.5.5 to 0.6.3 turned out to break Guile-SSH
> 0.6.0. I attach some of the test logs. Any idea what’s going on?
Well, I think the problem is that there are changes in the API between
libssh 0.5 and libssh 0.6. So Guile-SSH must be updated to be able to
work with lib
Artyom Poptsov skribis:
>> Upgrading libssh from 0.5.5 to 0.6.3 turned out to break Guile-SSH
>> 0.6.0. I attach some of the test logs. Any idea what’s going on?
>
> Well, I think the problem is that there are changes in the API between
> libssh 0.5 and libssh 0.6. So Guile-SSH must be updated
Artyom Poptsov writes:
>> Upgrading libssh from 0.5.5 to 0.6.3 turned out to break Guile-SSH
>> 0.6.0. I attach some of the test logs. Any idea what’s going on?
>
> Well, I think the problem is that there are changes in the API between
> libssh 0.5 and libssh 0.6. So Guile-SSH must be updated
Hello Artyom,
Upgrading libssh from 0.5.5 to 0.6.3 turned out to break Guile-SSH
0.6.0. I attach some of the test logs. Any idea what’s going on?
TIA,
Ludo’.
===
Guile-SSH 0.6.0: tests/test-suite.log
===
# TOTA
FYI, I upgraded libssh to the latest version in master, to fix a
security flaw. Since then, I tried building guile-ssh for the first
time. It fails its test suite. I guess this may have been caused by
the libssh upgrade. I don't have time to look into it right now, but I
don't think we should c
