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

ScyllaHide OutputDebugStringA protection for OllyDbg 2.0 doesn't work #54

Open
trietptm opened this issue Mar 16, 2018 · 1 comment
Open

Comments

@trietptm
Copy link

trietptm commented Mar 16, 2018

Hi, I use ScyllaTest_x86.exe and see that ScyllaHide OutputDebugStringA protection for OllyDbg 2.0 doesn't work.

snap 2018-03-16 at 15 35 47

snap 2018-03-16 at 15 36 01

This problem was mentioned in Twitter 4 years ago too: https://twitter.com/AshAbdalhalim/status/494700460838625280

@Mattiwatti
Copy link
Member

Checking this fixes it for me:

lol_olly

Alternatively you can just select 'don't consume any' which is the same as checking all three boxes in Olly v2 or all infinity boxes in Olly v1.

I will leave this open for now because I discovered that OllyExceptionHandler (which is supposed to be a hook in Olly's debug loop to fix stuff like this) is never installed at all for most of the default profiles. There is still a check for each individual setting within the hooked loop itself so you wouldn't get any unwanted changes in behaviour, and as far as Olly hacks go it is a work of art compared to some of the shit found in olly1patches.cpp.

I think it makes sense to apply the debug loop hook in Olly no matter what, given how broken some of it is by default. But I never use Olly myself so I'm a bit lost re: what would be reasonable/useful settings to enable for the default profiles.

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