Sandboxie+ Release v0.8.0 / 5.50.0

[bjm_]

Sandboxie + Release v0.8.0 / 5.50.0​

https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.8.0​

Note: Latest release​

Release Release v0.8.0 / 5.50.0 · sandboxie-plus/Sandboxie

This build fixes many issues and brings usability improvements. If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new b...

github.com

 

[franz]

Sandboxie + Release v0.8.0 / 5.50.0​

https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.8.0​

Note: Latest release​

Release Release v0.8.0 / 5.50.0 · sandboxie-plus/Sandboxie

This build fixes many issues and brings usability improvements. If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new b...

github.com

My f-secure safe block this file: SbieSvc.exe in Sandboxie-Classic-x64-v5.50.0. I run the file at VirusTotal and it seems fine but, is it a false positive?

 

[bjm_]

My f-secure safe block this file: SbieSvc.exe in Sandboxie-Classic-x64-v5.50.0. I run the file at VirusTotal and it seems fine but, is it a false positive?

https://www.f-secure.com/us-en/business/support-and-downloads/submit-a-sample

 

[franz]

https://www.f-secure.com/us-en/business/support-and-downloads/submit-a-sample

Thank you very much..

 

[plat]

I don't know if this is part of the F-Secure issue but the developer of NVT OSArmor suggested the Sbie dev also look into getting the .tmp setup file signed, not just the main .exe. I also have a problem w/SmartScreen and Sbie downloads, even though he got his cert signed a while ago.

Well, these things can get a little pricey, I guess.

Source

 

[franz]

I don't know if this is part of the F-Secure issue but the developer of NVT OSArmor suggested the Sbie dev also look into getting the .tmp setup file signed, not just the main .exe. I also have a problem w/SmartScreen and Sbie, even though he got his cert signed a while ago.

Well, these things can get a little pricey, I guess.

Source

Thank you for the info, I just send in the file, so I have to wait for the respones form f-secure..

 

[franz]

Thank you for the info, I just send in the file, so I have to wait for the respones from f-secure..

 

[franz]

I had to run the diagnostic tools in f-secure to gather more information from the affected system, and send the result to f-secure so they could further check.

 

[bjm_]

v0.8.0 / 5.50.0 is now labeled Pre-release

Release v0.8.0 / 5.50.0
Note: Pre-release

 

[franz]

This is the response from f-secure:
The detection occurs because the process "SbieSvc.exe" is trying to modify F-Secure processes (nif2_ols_ca.exe)

The detection will keep occurring even though the executable is already marked as clean in our system (because of the modification it tries to make to our program). As of this, the best solution would be to exclude the program directly.

In our case, the best option is to exclude the sample (SbieSvc.exe) directly through its path+filename.

 

[bjm_]

In our case, the best option is to exclude the sample (SbieSvc.exe) directly through its path+filename.

btw ~ I've had Sandboxie-Plus/Sandboxie-Classic installers and entire installed folders excluded with my security solution since DavidXanatos builds.