Nope, anything with tif is done. I done know everything about it, other then it was COMPLETELY patched up. This wouldnt work for a number of reason, when you ran the tiff you saved it as your wallpaper, this made it go into memory . This is what was able to run code and launch h.bin . Just looking at it wont solve anything. We have already tried inserting code into gif and such, and viewing it with the browser, we are able to, but then nothing works. Someone found a great piece on goggle about it, although I dont remember in which thread it was. The piece fully explained everything, and why we cant run it again, pretty much.

__________________

Ihate2.5, i was talking about embedding the old 1.5 libungif into a homebrew program, and calling effectively the old 1.5 version to display the tiff. See what I mean.....

__________________

Sorry Ihateusing2.5 i didnt understand what "there goes your answer means".

Again I may be wrong, but if the libungif is still fragile, using the OLD 1.5 libungif section of the library injected into a howbrew, we would effectively recreate the exploit. assuming as i said they patched the libungif library and not the kernel, to which the overflow exploit leads has not been patched.

__________________

They patched the libtiff library, which means that any of the built-in software that uses libtiff will not suffer from the exploit.

Your idea would work, except for one flaw - you need to somehow be able to execute your libtiff-homebrew app, to activate the exploit. If you're able to execute your libtiff-homebrew, then why bother with libtiff - you already have homebrew capability.

In other words - it can't work, because you have no way to execute your crafted libtiff app.

i love you fanjita

Ok there goes your answer by fanjita. Same as mine, it cant work. You can read my shitty explanation, or Fanjitas perfect explanation

__________________

Fanjita has always answers to our question...
We love you Fanjita.

__________________

Fanjita seems all loved up..

Fanjita , thanks for your comments. I believe the work your doing is great.

I dont have the coding expertise to do this, but if your right in what your saying. I belive that the older library's for libuntiff are still vunerable. if we were to put the calls into a homebrew to call a new modified version of the libuntiff, this would lead to the execution of the exploit through a homebrew app. It would call the tiff file at a specified location (not like the browser). Thus enablabling overeflow.tif to once again to overflow, purely for a method of downgrading.

I think the work you have achieved todate if fantastic from a homebrew point of view, but there are still a wealth of features available to us on 1.5, as apposed to 2.01+.

Im just pondering the motions of a possible downgrade method.

__________________