Hello All,
We have our applications on Powerbuilder 2019. Due to third party requirement, we need to scan our code for vulnerabilities using any 'Source code Analysis tools' and generate report. I didn't find any tool for PB scripts.
Can anyone kindly suggest if there is any possible way to convert the code to C/C++/C# and run against the scanning tool.
We are neither expecting the converted code to run nor have full functionality. But just want to run against the scanning tools and find out security flaws.
Thank you so much in advance.
Can you kindly help me with 2 questions regarding your answer in that thread. Or do you want me to post the questions in that thread itself?
1. Is the conversion still possible with the Powerbuilder 2019 or only in the older version i.e., 12 or earlier?
2. Can you kindly help me with the MS project step - Once we compile the application in machine code, do we need to use MS project and take the machine code files to convert into C++ exe?
I'm sorry for this question as I have always used Pcode and never machine code.
1) The C++ compile feature is still in PB2019 and it's *not* a conversion but, merely a compile option (machine code) in your "Project" object maintained by the Project Painter. Once you select an M-Code compile for the PB App's EXE - the IDE does the rest by outputing C++ source based on your PowerScript and Class definitions in the related PBL's (auto-magically). That C++ source is then compiled my the standard MicroSoft C++ compiler via a MS-Build process.
The key aspect during the C++ compilation process is to skim off the C++ *source code* and then feed that into a vulnerability software product like I mention in the former thread. I have been doing this for years when I was consulting with the Canadian Federal Government before joining Appeon. There is no way we could get any PB Apps into production without what the government calls a TRA (Threat & Risk Assessment). Part of the TRA is a software venerability scan. Note that this also happens in the TRA process for the PB run-time DLL's as well which are also C++ based.
2) The vulnerability procedure that I have suggested does not require any use of any further MS products.
HTH
Regards ... Chris