You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Thanks for taking the time to develop this tool. Unfortunately, the latest syswhispers2 update has changed its output to be split between x86 and x64 syscalls, and it has also changed the output naming. This is what Syswhispers2 looks like when run with the commands included in the README.
$ python3 syswhispers.py --preset all -o syscalls_all && cd ..
. ,--.
,-. . . ,-. . , , |-. o ,-. ,-. ,-. ,-. ,-. /
`-. | | `-. |/|/ | | | `-. | | |-' | `-. ,-'
`-' `-| `-' ' ' ' ' ' `-' |-' `-' ' `-' `---
/| | @Jackson_T
`-' ' @modexpblog, 2021
SysWhispers2: Why call the kernel when you can whisper?
All functions selected.
Complete! Files written to:
syscalls_all.h
syscalls_all.c
syscalls_all_stubs.x86.asm
syscalls_all_stubs.x86.nasm
syscalls_all_stubs.x86.s
syscalls_all_stubs.x64.asm
syscalls_all_stubs.x64.nasm
syscalls_all_stubs.x64.s
This breaks InlineWhispers2, because it now fails to read the correct output file when run.
Hello, I fixed it with an old version of SysWhispers2, thank you for your issue.
I know what is the problem about the new version, it will be updated later, I need to find time, I close this ticket but PRs are welcome if someone want to help about this issue.
Hello! Thanks for taking the time to develop this tool. Unfortunately, the latest syswhispers2 update has changed its output to be split between x86 and x64 syscalls, and it has also changed the output naming. This is what Syswhispers2 looks like when run with the commands included in the README.
This breaks InlineWhispers2, because it now fails to read the correct output file when run.
The text was updated successfully, but these errors were encountered: