I'm following up an issue I noticed with the V18 SBC running under Windows, that has just re-occurred since upgrading the SBC to V20 a few weeks ago.
After installing the SBC under Windows, the service is added and runs just fine.
The issue isn't with the SBC itself, but with the way the Windows service "Image path" shows in the registry.
By default, the Image path in the registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\3CXSBC is listed as:
C:\ProgramData\3CXSBC\3cxsbc.exe C:\ProgramData\3CXSBC\3cxsbc.exe C:\ProgramData\3CXSBC\3cxsbc.conf
This works and the service runs, but it triggers a false alert with one of our security tools as it thinks there is a space in the path to the executable, which is a security risk.
Obviously, there isn't a space in the path, though the full path to the executable filename is listed twice, which I suspect is triggering the false positive alert.
I found I can stop the false alert, and not affect the SBC service, by dropping one of the references to the exe - so the image path is just:
C:\ProgramData\3CXSBC\3cxsbc.exe C:\ProgramData\3CXSBC\3cxsbc.conf
With the Image path updated, the SBC service starts and runs without issue. And the false positive alert is cleared.
I'm not sure if this is a bug with the installer accidentally listing the exe path twice, or if it's been done for a reason. If there is a reason, I'll look for other ways to stop the false positive alert.
As I said, the SBC seems to run without issue if I modify the path.
After installing the SBC under Windows, the service is added and runs just fine.
The issue isn't with the SBC itself, but with the way the Windows service "Image path" shows in the registry.
By default, the Image path in the registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\3CXSBC is listed as:
C:\ProgramData\3CXSBC\3cxsbc.exe C:\ProgramData\3CXSBC\3cxsbc.exe C:\ProgramData\3CXSBC\3cxsbc.conf
This works and the service runs, but it triggers a false alert with one of our security tools as it thinks there is a space in the path to the executable, which is a security risk.
Obviously, there isn't a space in the path, though the full path to the executable filename is listed twice, which I suspect is triggering the false positive alert.
I found I can stop the false alert, and not affect the SBC service, by dropping one of the references to the exe - so the image path is just:
C:\ProgramData\3CXSBC\3cxsbc.exe C:\ProgramData\3CXSBC\3cxsbc.conf
With the Image path updated, the SBC service starts and runs without issue. And the false positive alert is cleared.
I'm not sure if this is a bug with the installer accidentally listing the exe path twice, or if it's been done for a reason. If there is a reason, I'll look for other ways to stop the false positive alert.
As I said, the SBC seems to run without issue if I modify the path.
