cquirke (MVP Windows shell/user) wrote:
Rick Chauvin wrote:
[....]
I vote to get it fixed properly though so that those two dll's are
inclusive of all Numerous Updates that are Missing if swapped
If I had resources to fix this (as one presumes MS has) I'd do this:
- get documentation on what's changed in those two .DLL
- any crucial exploits that depend on those files to fix?
- determine most recent .DLL that work via the fix (IE 5.5 SP2?)
...any version of those dll's from 5.5 worked just fine, it was the first
release of IE6 and absolutely irregardless of what others think, even SP1
still has the same exact problem. About the dll's though and mostlikely it
is them, but just because swapping the dll's do appear on the surface to
eliminate the problem does not mean 100% it is the dll's that's the issue in
the first place - it could be other things closely related. In circuit
troubleshooting and no doubt it's the same with software, I've seen time and
time again where you think it may be one component causing a problem where in
the end it may end up have been another down the line causing the
malfunction. Always had to keep an open mind.
- FC these against the IE 6 ones that don't work
- see if what FC finds can be mapped to particular functions
- if offset dependencies allow:
- paste across functions from IE 6 to old until old breaks
- paste across functions from old to IE 6 until IE 6 works
- zoom in and disassemble the problemetic function
- see if a logic error etc. can be found
- fix the function and issue fixed .DLLs as on-request hotfix
- after testing, issue as downloadable hotfix, then WinUpate
Okay, sounds good to me
Who's the programmer at MS that has the know how
and access to do this?
Chris, would you do me a favor, there is the other thread in this group that
has two conversations going on within it, if you want to please read it and
reply to your other fellow MVP's as to any pertinent facts that you can help
let them know there is a problem, because as it stands surprisingly to me
they do not think there is a problem at all and that it was already fixed -
which I am baffled at why they think that.
Please look for this header:
From: "Jerry Bryant [MSFT]"
Newsgroups: microsoft.public.win98.gen_discussion............. ...
Sent: Saturday, March 26, 2005 2:06 AM
Subject: MS05-002 on 9x and ME
Thank you,
Rick
MS wouldn't have to hack around with FC, given they'd have the source
code. It would also be easier from them to read up on what changes
were made to these .DLL, and whether any exploits need these changes
to remain blocked. It would be a sad commentary on MS, if within a
few months of reading this post, somene ITW came up with a fix, even
though they lacked MS's advantage of source code and documentation.
Well, there's the gauntlet. Anyone care to pick it up? :-)
---------- ----- ---- --- -- - - - -
Gone to bloggery: http://cquirke.blogspot.com
---------- ----- ---- --- -- - - - -