Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

1. Closed: NOT a BUG | 2. Closed: NOT a BUG | 3. Closed: NB (DOSX)

posted by DOS386(R), 20.06.2008, 09:51

> > > dpmild32 doesn't care about the PE "readable" bit
> > COOL ... but what does this code do ?
> > Maybe it skips my evil non-readable section ?
> Yes.

The truth is out :-|

> Or just set this boring "readable" bit in your app ...

Done 10 days ago (RTFS) :clap: ... I don't refuse to fix "my" bug ... but doing so won't fix the bug ("vulnerability") in DPMILD32

> > idea would be in DPMILD32 to check the page block fixup sizes
> Ok, might be considered...


> > - Always clear the stack
> I'm not sure if this is a good idea. If helps with buggy applications
> only, which fully deserve to crash and die

No :crying: please don't shoot everybody who isn't perfect. Leaving the stack random can raise random very-hard-to-debug bugginess, allows bugged apps to behave differently depending of "first run" or "non-first run" or other apps ran previously, what IMHO is very bad :crying: Clearing the stack + adding hack to fill it with mess instead makes the apps behave deterministically and helps to debug those buggy applications and brings up the evidence of bug allowing to fix or shoot them then :-D

This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***


Complete thread:

Back to the forum
Board view  Mix view
15296 Postings in 1378 Threads, 254 registered users, 8 users online (0 registered, 8 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum