Hello Appeon Support,
We have a large thick-client PowerBuilder application, written many years ago, that our Security Team have raised a risk against.
The risk is “DLL Hijacking”
This application is built and deployed as 1 x Exe + numerous PBD’s, + all the associated DLL’s (e.g. libjcc.dll, pbapl.dll, pbvm.dll etc)
Is there some way these DLL’s can be “signed” to prevent a hacker from inserting their own DLL in place of a legitimate DLL ?
We believe this is possible by using PowerClient (please confirm) – but we are searching for a simpler solution than PowerClient.
Many Thanks
#2 I don't know what the PB Runtime does if it detects one of the DLLs has been altered.
And can these tools be integrated into the build process/pipeline ?