- User Since
- Oct 10 2018, 11:33 AM (107 w, 9 h)
Jun 24 2019
@Jakuje : FTR, we test this in i386 chroots or containers, the base system is 64 bit everywhere. It could be specific to the Debian/Ubuntu valgrind version or toolchain of course.
May 27 2019
For the record, this also happens with the latest 0.8.7. I added a reproducer to the Debian package, to be able to track this easily.
Oct 21 2018
I can confirm that with libssh master, both the reproducer and cockpit's unit tests work. Thanks! As this blocks releasing new cockpit versions, and fixes a regression, do you plan to fix this in Fedora soon? I'll file a bug for the next RHEL devel version.
Oct 19 2018
reproducer code and script:
Oct 10 2018
IMHO the expected behaviour would be to check both the global and user file, like ssh_session_is_known_server(). Otherwise, actually checking the global file on the caller side would be rather ugly: You would first need to temporarily set the *user* known hosts to the global one (/etc/ssh/ssh_known_hosts), check ssh_session_has_known_hosts_entry(), then reset the user known hosts file to the default again, and check again.