Skip to content

PowerShell: Pipe/stream encoding issues with ciphertext to stdout or from stdin #16

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

Closed
juneb opened this issue Oct 3, 2017 · 1 comment

Comments

@juneb
Copy link
Contributor

juneb commented Oct 3, 2017

In a PowerShell console, the following command patterns generate 'Unsupported type 63 discovered in data stream' errors:

  • 'hello' | aws-crypto -e -m key=$cmkArn -i - -o - | aws-crypto -d -i - -o -

  • $encrypted = 'hello' | aws-crypto -e -m key=$cmkArn -i - -o -
    $encrypted | aws-crypto -d -i - -o -

Converting the intermediate output to base 64 doesn't help. Neither does changing the $OutputEncoding automatic variable to UTF-8.

@mattsb42-aws mattsb42-aws changed the title PowerShell: Piping from stdin to stdout generates unsupported type error PowerShell: Pipe/stream encoding issues with ciphertext to stdout or from stdin Oct 8, 2017
@mattsb42-aws
Copy link
Member

This will be addressed by #29.

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