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

Added token generation compatibility for Linux & MacOS #20

Merged
merged 1 commit into from
Dec 1, 2023

Conversation

agreenbhm
Copy link
Contributor

Linux and MacOS use UTF-8 rather than Windows Powershell UTF-16. Due to the extra null bytes from UTF-16, password conversion from SecureString to plaintext was terminating after the first character on Linux. This commit adds a check to determine if the host system is Windows or Linux/MacOS. If Windows, the original logic runs. If Linux or MacOS, a different method for converting a SecureString to plaintext is performed.

Linux and MacOS use UTF-8 rather than Windows Powershell UTF-16.  Due to the extra null bytes from UTF-16, password conversion from SecureString to plaintext was terminating after the first character on Linux.  This commit adds a check to determine if the host system is Windows or Linux/MacOS.  If Windows, the original logic runs.  If Linux or MacOS, a different method for converting a SecureString to plaintext is performed.
@UpperM UpperM merged commit 8de6b6f into UpperM:master Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants