-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PATCH] sftp: fix connection memleaks #3581
Comments
|
Is it possible to split this patch into several ones with independent issues? |
sure, I will do so. |
|
|
|
|
|
Thanks!
Branch: 3581_sftp_fixes |
Hi Andreas,
Maybe you will find it interesting to have a look at this Debian bug, which also has to do with SFTP:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774135
So, in essence, the user is running Debian x32 (!) and there SFTP is completely broken. Probably this happens due to some type size weirdness on x32, because we can't reproduce it on i386 and amd64.
--Yury |
Replying to zaytsev:
I've added fix of config file reading. I don't think that it fixes that bug, but who knows. |
Some new info from the Debian bug, with 4.8.15 it looks like this:
Asked to test with the latest 3581_sftp_fixes branch... |
Can Thorsten test following patch?
when reading ssh_config with matching host entry mc do bad pointer arithmetic |
|
|
Merged to master: [ab0c2af].
|
|
Important
This issue was migrated from Trac:
and
1) open_connection abort not handled correct yet
2) missing libssh2_session_free() on close_connection
3) internal list from libssh2_userauth_list() must not freed by mc
4) cosmetic: re-order open_connection and close_connection steps
5) cosmetic: sftpfs_super_data created at sftpfs_cb_open_connection() was freed at sftpfs_close_connection()
6) add FIXME for deprected libssh2_session_startup() since libssh2 1.2.8
found by Clang/AddressSanitizer
Note
Original attachments:
and
onJan 3, 2016 at 15:57 UTC
and
onJan 3, 2016 at 18:00 UTC
and
onJan 3, 2016 at 18:00 UTC
and
onJan 3, 2016 at 18:00 UTC
and
onJan 3, 2016 at 18:01 UTC
and
onJan 3, 2016 at 18:01 UTC
and
onJan 11, 2016 at 21:11 UTC
The text was updated successfully, but these errors were encountered: