Re: PIMAGE_IMPORT_DESCRIPTOR

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Has,

Thanks for your feedback.

Yes, I have talked with our Side-by-Side team for this issue. They
confirmed our guess. There is a Publisher policy that decided to move
forward to the newer version.

As to the wacky stuff on the end of the path, that "x-ww" is the
"worldwide" or "culture neutral" culture marker. The very last number is a
hash of the complete identity of the component.

We should not worry about how the hash is generated; ignorance is bliss in
this case, and we should neither attempt to reverse-engineer it nor
hardcode the paths anywhere, including the registry.

Hope this information makes sense to you.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

.

Relevant Pages

  • Re: PIMAGE_IMPORT_DESCRIPTOR
    ... > Thanks for your feedback. ... > hash of the complete identity of the component. ... including the registry. ... > Best regards, ...
    (microsoft.public.win32.programmer.kernel)
  • RE: QPopper 4.0.x buffer overflow vulnerability
    ... Instructions can be found at http://www.networkdweebs.com/chroot.html ... > Hash: SHA1 ... >> Feedback is welcome. ...
    (Bugtraq)
  • Re: Fast 32-bit Hash
    ... >> a cryptographic hash, does anyone see any obvious attacks or other ... > I used your hash like a prng: ... Applying feedback around ...
    (sci.crypt)
  • Re: [SLE] JPilot - Cant synch
    ... Hash: SHA1 ... but at least now I'm getting some feedback. ... synch, ...
    (SuSE)