CODEWITHSUNDEEP
install4j
munter
munter

Reputation: 11

install4j to avoid loading DLLs from installation directory

The Install4j (v8) executable (e.g. Client.exe) apparently loads DDL from the Windows system folder \System32\ as well as from the installation directory of our application. According to the audit findings, there is a risk that the executable will call a corrupted DDL provided in the application directory instead of the one from the Windows system. Q: Is there any way to prevent "local" DDLs from being loaded?

I guess this is MS Windows default behaviour and we can only consider a locking mechanism on the installation folder (read-only). This would bring additional challenges as the application may want to write logs there...

Upvotes: 0

Views: 42

Answers (0)

Related Questions