Open
Conversation
This fixes a bug with scapy and the ctypes update of python>=3.9.1. Instead of requiring `liblibc.a` scapy uses the correct `libc.a` library. https://bugs.python.org/issue42580
pepper-jk
force-pushed
the
libc_scapy_fix
branch
from
f581409 to
c84fa4a
Compare
Collaborator
Author
|
Merging it right after I fix whatever problems it caused. 🙈 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a bug with scapy and the ctypes update of python>=3.9.1.
When executing
id2tunter python3.9.1or above (3.10.5in my case), you got the following error:FileNotFoundError: [Errno 2] No such file or directory: b'liblibc.a'This was due to an issue with the python ctypes.
The workaround for this is to link
libc.atoliblibc.aas described here:$ cd /usr/lib/x86_64-linux-gnu/ $ sudo ln -s -f libc.a liblibc.aor in path
/usr/lib/for my arch system at least.The stackexchange solution had been posted here before #111 (comment) and was deemed the solution back then.
However, the proper way to fix this for all users is updating
scapyto version2.4.5.Instead of requiring
liblibc.ascapy now uses the correctlibc.alibrary.Now issue #111 is resolved for good.