Catsxp red box 2 issues
- Thread starter Mr.X
- Start date
If I recall correctly, you were the one who pursued having that setting added. Just to confirm, would you now prefer to have it removed instead?
github.com
Update Templates.ini · sandboxie-plus/Sandboxie@d469163
- Added "Catsxp browser" due to a user request.
github.com
First I want to know what that setting does in the first place...
Is this correct?
I don't how bad is to remove such template and not having those special hardcoded workarounds.
Is this correct?
added "SpecialImage=chrome,some_electron_app.exe" option to sandboxie.ini, valid image types "chrome", "firefox"
-- with this option you can enable special hardcoded workarounds to new obscure forks of those browsers
Release Release v0.5.3 / 5.45.2 · sandboxie-plus/Sandboxie
This is a maintenance release it brings some small new features and fixes many minor issues. The plus installer was improved it now provides a extract function and creates the required Sandboxie.in...
I don't how bad is to remove such template and not having those special hardcoded workarounds.
This may improve compatibility if Catsxp does not work well with all Chrome-specific handling. However, after removing the line, Catsxp may be treated as a normal application unless Sandboxie detects it automatically.
With the line removed:
-
-
- If neither detector recognizes it, Catsxp remains unclassified and does not receive image-type-specific Chrome behavior.
The difference can affect compatibility features such as Chromium command-line flags, Chrome Secure Preferences handling, desktop and WindowStation workarounds, Win32k hooks, WebView2 handling, and other browser-specific paths. It does not disable Sandboxie’s general isolation.
In practice, removing this one line is a targeted compatibility test. It may help if forced Chrome classification is causing Catsxp problems, but it may also remove compatibility handling that Catsxp needs. The result depends on whether, and when, one of Sandboxie’s automatic detection paths classifies the application.
With the line removed:
-
UseElectronDetection=y may still detect Catsxp during startup if its executable directory contains recognizable Chromium or Electron files. If detected, Sandboxie assigns the same Chrome image type, so the result will be mostly the same as keeping the explicit rule.-
DynamicImageDetection=y may detect it later when it loads chrome_elf.dll or a matching renamed Chromium DLL. In that case, Catsxp may run as a normal application during early startup. Some runtime Chrome-specific handling may begin only after detection, while startup-only handling may already have been skipped.- If neither detector recognizes it, Catsxp remains unclassified and does not receive image-type-specific Chrome behavior.
The difference can affect compatibility features such as Chromium command-line flags, Chrome Secure Preferences handling, desktop and WindowStation workarounds, Win32k hooks, WebView2 handling, and other browser-specific paths. It does not disable Sandboxie’s general isolation.
In practice, removing this one line is a targeted compatibility test. It may help if forced Chrome classification is causing Catsxp problems, but it may also remove compatibility handling that Catsxp needs. The result depends on whether, and when, one of Sandboxie’s automatic detection paths classifies the application.
Well, why don't you add support for PORTABLE Catsxp?
Meaning, add a fix for both issues I encountered for the portable browser.
That said, I think there's no need to remove the template.
Portable Catsxp browser:
Meaning, add a fix for both issues I encountered for the portable browser.
That said, I think there's no need to remove the template.
Portable Catsxp browser:
Last edited:
Also, I think my other portable browser (catsxp_UncensoredDNS.exe) does not have both issues because SBIE doesn't detect it to apply the SpecialImage template. Dunno. I think because the executable was renamed as catsxp_UncensoredDNS.exe.
Am I right?
Edit:
I added to my ini file this line: Template=SpecialImages
SBIE still doesn't detect it, I think due to the different name, catsxp_UncensoredDNS.exe.
If I'm right, I think it's better for SBIE to retrieve the Original Filename, not the Name.
Am I correct?
Am I right?
Edit:
I added to my ini file this line: Template=SpecialImages
SBIE still doesn't detect it, I think due to the different name, catsxp_UncensoredDNS.exe.
If I'm right, I think it's better for SBIE to retrieve the Original Filename, not the Name.
Am I correct?
Last edited:
Sandboxie already loads
However, if removing
If removing the original rule resolves the problem, the correct solution is to leave it removed. There is no need to add a separate rule for the renamed executable unless testing shows that it is specifically required and does not reintroduce the issue.
Template=SpecialImages by default, so adding the same entry to your configuration will not change the behavior. If you need to classify a differently named browser as Chrome, use the appropriate rule, for example:SpecialImage=chrome,catsxp_UncensoredDNS.exeHowever, if removing
SpecialImage=chrome,catsxp.exe fixes the problem when the browser uses its original executable name, why add another SpecialImage rule for the renamed executable that could cause the same issue? I do not understand the intended outcome.If removing the original rule resolves the problem, the correct solution is to leave it removed. There is no need to add a separate rule for the renamed executable unless testing shows that it is specifically required and does not reintroduce the issue.
Fine. Remove it. Thanks.
This concerns me. So I still don't understand why my two issues can't be fixed without removing SpecialImage=chrome,catsxp.exe
I'll test this browser soon
Catsxp portable, latest release:
Did you test it?
Is this issue fixed in SBIE+ 1.18.3?
New version:
you can use SpecialImage=none,catsxp.exe in sandboxie ini to disabel the detection from the templates.ini
is the issue solved for you by simply not having catsxp.exe identified as chrome? if so then i shoudl just remove that entry from templates.ini?
is the issue solved for you by simply not having catsxp.exe identified as chrome? if so then i shoudl just remove that entry from templates.ini?
