Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration file error in line 1: line too long (UTF8 encoding) #461

Closed
isaak654 opened this issue Jan 28, 2021 · 6 comments
Closed

Configuration file error in line 1: line too long (UTF8 encoding) #461

isaak654 opened this issue Jan 28, 2021 · 6 comments
Labels
Status: Added in Next Build Added in the next Sandboxie version

Comments

@isaak654
Copy link
Collaborator

isaak654 commented Jan 28, 2021

Problem: if you change Templates.ini encoding to UTF8 or UTF8-BOM, Sandboxie will produce errors like this:

utf8_not_supported

Some advantages to support UTF8 encoding:

  1. It would allow to save storage space:
    storage_space
  2. It would allow to resolve the corruption issue mentioned in Fixed German spelling for Text-German-1031.txt #402
  3. Changing Templates.ini encoding to UTF8-BOM (with Sandboxie Classic installed) can trigger multiple dialog windows that you can't even close, unless you terminate Sandboxie Control from Windows Task manager. Another reason to support UTF8 encoding.
@DavidXanatos
Copy link
Member

I'm not sure how expedient that would be, the files are parsed by the driver directly and I would guess that may be some required UTF8 to Unicode functions may nto be available. In the kernel mode you cant use most of the normal windows facilities.

@isaak654
Copy link
Collaborator Author

I'm not sure how expedient that would be, the files are parsed by the driver directly and I would guess that may be some required UTF8 to Unicode functions may nto be available. In the kernel mode you cant use most of the normal windows facilities.

An attacker could craft a small script to convert the template file in utf8-bom and screw up your Sandboxie Classic configuration.
Fortunately I wasn't able to trigger the dialog windows loop on Sandboxie Plus, but Classic users should be concerned about this.

@DavidXanatos
Copy link
Member

Well the attacker would have to be outside the sandbox and have admin rights so he can break whatever he wants

@isaak654
Copy link
Collaborator Author

isaak654 commented Jan 28, 2021

Well the attacker would have to be outside the sandbox and have admin rights so he can break whatever he wants

Good point, but there is the issue mentioned in #402.
I provided a workaround for it, but it could still be confusing for some users.

@DavidXanatos
Copy link
Member

I'm not saying no, yet, I'll have to look into it.

also I'm very hesitant changing things that may royally screw up something that may result in som odd hard to reproduce bugs.

@DavidXanatos
Copy link
Member

Sooo adding utf8 to the driver is a mess but doable, in the end I need to "manually" do the utf8 to unicode decoding

@DavidXanatos DavidXanatos added the Status: Added in Next Build Added in the next Sandboxie version label Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Added in Next Build Added in the next Sandboxie version
Projects
None yet
Development

No branches or pull requests

2 participants