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

HardeningKitty on non-english Windows #35

Closed
mrsheepsheep opened this issue May 4, 2021 · 2 comments
Closed

HardeningKitty on non-english Windows #35

mrsheepsheep opened this issue May 4, 2021 · 2 comments
Assignees

Comments

@mrsheepsheep
Copy link

mrsheepsheep commented May 4, 2021

First, great work ! HardeningKitty is such a cute little thing.

As you mentioned in the readme, HardeningKitty may not support languages other than english, due to the fact that Windows is not consistent in its output depending on the installed system language...

A "quick" fix for most hardening lists is to translate files into the desired language. This mostly concerns finding methods with a localized result, such as accesschk or auditpol.

In terms of following new commits on these files, how would you translate the lists ?

Second problem that may or may not be a big issue : accesschk only supports ANSI encoding. Any accentuated character such as é and è (widely used in French for example) is not output correctly. In this case, é becomes ù and è is not printed. Same for apostrophe ' becoming ?. Standard encoding issues...

AccesschkANSI

As you can see, the NT AUTHORITY\System - which translates as AUTORITE NT\Système is output as AUTORITE NT\Systme.
While replaced characters can be (unsafely) replaced, missing characters cannot be recovered...

I was hoping there was a way to enforce encoding for the accesschk binary, but haven't found any working solution. Microsoft seems to be aware of the encoding issue, but no update since last year...

The issue on its own is not related to HardeningKitty, but it could be mitigated in the script, if anyone has an idea.

@0x6d69636b
Copy link
Owner

Thank you for your feedback and this issue. I have "feared" to receive such an issue soon and am currently working on a SID translation for accessk. As soon as I am ready, I would be happy for a test on your system

@mrsheepsheep
Copy link
Author

#36 should be more appropriate to follow the issue, thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants