fix(pwsh): fix reading .pem files from PowerShell runspace #859
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we call Encoding.GetString(byte[]) from a C# PowerShell runspace (e.g. DPS Console), we are getting the following error:
I don't know why. This results in an empty
$PemData
which obviously can't be parsed.The workaround is to read the certificate and private key file directly as UTF8, rather than getting the UTF8 representation of the data.