Skip to content
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

INT2D #34

Closed
OmuZer opened this issue Aug 1, 2023 · 2 comments
Closed

INT2D #34

OmuZer opened this issue Aug 1, 2023 · 2 comments

Comments

@OmuZer
Copy link

OmuZer commented Aug 1, 2023

Hi, i have a program which is using the INT2D for anti debug. And while running tiny_tracer under the application i confirmed its INT2D anti debug.... Is there any workaround to this? Thanks. EDITED (I saw the hide branch, but it seems so the INT2D flag is not cleared.)

@hasherezade
Copy link
Owner

hi @OmuZer !
I added logging about those interrupts. Example:

cbbd;kernel32.SetLastError
10133;ntdll.RtlLeaveCriticalSection
8dcc;INT:2d
1011f;ntdll.RtlEnterCriticalSection

Once you have it tagged, you can just patch it out.
For now I am not planning on adding automatic bypasses for any AntiDebug techniques, only to inform about them. Maybe in the future.

@OmuZer
Copy link
Author

OmuZer commented Aug 12, 2023

@hasherezade, Sorry for the late reply. I was busy, but i saw that commit for the logging of "interrupts instructions" that is very helpful, thanks so much! I really appreciate it :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants