"Verifying the signature verifies the hash of the file. It allows you to
change the exact file as long as the signature is still valid. The behavior
you see is by design."
Checking the hash on an unsigned file means it has to be exactly the same
file when "burned". Not so for a signed file. This s
Verifying the signature verifies the hash of the file. It allows you to
change the exact file as long as the signature is still valid. The behavior
you see is by design.
I don't understand your comment about failing the local check it should use
the download URL. That is what the wixstdba.dll does
I have an MSI in a chain but Burn loaded an old local copy with the same
name. From what I understand it should not have loaded this payload
because the hash should not match. I checked the CachePayload burn code
and it looks like it doesn't check the hash if the certificate is
correct. I think
3 matches
Mail list logo
