Windows libraries resource modification causes security reputation problems about esky

[rfk]

It's not entirely clear to me why this is happening. Does it occur for all instances of the python27.ddl or only for the one copied into the top-level bootstrap environment?

[marioballano]

It happens to all of them, I just generated a bundle and I can see how both the python27.dll copied into the top-level bootstrap environment and the one copied into the specific version share the same hashes and have the modified resources, I will try to allocate some time to research on my side too.

[marioballano]

I dug further and found that the actual culprit is py2exe, under the scenes it modifies the python dll resources by calling patch_python_dll_winver() within the build_exe module, it's still not fully clear to me why they need to patch it but I believe it may have something to do with the library missing its resources after being UPXed or packed among other things.

anyhow, I ended up modifying py2exe so the python library remains on its original shape, it seems to do the trick for my particular setup. afaik py2exe is no longer maintained and it doesn't look to me like we should handle this on the esky side, closing this issue unless you have some other suggestions.

thanks for your support!