-
Notifications
You must be signed in to change notification settings - Fork 129
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
Use proper UTF-8 to UTF-16 conversion? #96
Comments
@rgl, I'm not really versed into Windows encoding (nor UTF-16). From what I understand this code is building a pure UCS-2 (wide char) string with the topmost byte being always 0. This will indeed fail with any character > 127, which is unfortunate. I think this can be fixed with this: wideCmd := utf16.Encode([]rune(psCmd)) Hopefully the result will be in proper endian for the receiving machine. Would you mind testing this, as I'm very illiterate about everything related to powershell ? |
Windows uses UTF-16LE and utf16.Encode is UTF-16BE. I will submit PR soon. |
Oh an I was mistaken, |
@rgl I'm lost, your PR implements a BE->LE conversion, but your last comment here seems to imply it wasn't needed. Can you elaborate? |
Sorry for the confusion... the PR does not really convert from BE to LE. Let me clarify:
|
Can
winrm/powershell.go
Lines 10 to 23 in 1d17eaf
The text was updated successfully, but these errors were encountered: