-
Notifications
You must be signed in to change notification settings - Fork 116
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
Intercept works with libc 2.29-4 but not with libc 2.30-1 #97
Comments
Hi @mavy , could you show us a disassembly of your libc around that specified address |
Of course:
|
Thank you. Yes, there is a scenario in that code listing around the |
We cannot move right-away to Ubuntu 20.04 because * lib syscall_intercept doesn't work with more recent libc See issue pmem/syscall_intercept#97. Proposed change is not merged yet (though appears to work, so we could go to that specific commit) * scapy operation seems to have issues where an ACK goes out automatically before our SYN+ACK response to the incoming SYN. Also, there are other problems building scapy on 19.10. Let's differ the move to 20.04 LTS to a later time. Signed-off-by: David Verbeiren <david.verbeiren@tessares.net>
I think I'm still running into this issue, has it been fixed? I'm using Ubuntu 22.10 using GNU libc 2.36 inside WSL v1. |
After upgrading
libc
to2.30-1
, I am seeing the next message :not enough space for patching around syscal libsyscall_intercept error
The log has the next contents:
Going to the previous version of glibc shows the correct behaviour:
The text was updated successfully, but these errors were encountered: