Skip to content

Reject malformed Base64 padding consistently on Windows PowerShell - #32

Merged
stadub merged 1 commit into
base64tring/developfrom
fix/base64-windows-padding
Nov 11, 2026
Merged

stadub merged 1 commit into
base64tring/developfrom
fix/base64-windows-padding

Conversation

@stadub

@stadub stadub commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Windows PowerShell 5.1/.NET Framework accepted Zm8== even though the existing malformed-input regression requires rejection. Hosted release-candidate run 43073726291 reproduced this difference while the other three runtimes passed.

Validate normalized padded input length and terminal padding shape explicitly before delegating decoding to .NET. Preserve the previously reviewed PR #28 encoding/pipeline behavior and all 31 existing regressions; add three over-padding/padding-only cases. This follow-up contains no out/ artifacts and targets the module development branch.

The source-only, credential-free workflow validates source and an ephemeral generated package on Windows PowerShell 5.1, Windows pwsh, Linux and macOS. Local macOS pwsh 7.7.0/Pester 4.10.1 passes all 34 regressions.

References #22 and #29. No issue closure, Gallery upload or master change is requested. After this follow-up passes, selectively port the reviewed guard/tests to the 1.3.0 release candidate and regenerate its package.

@stadub
stadub merged commit 51b283c into base64tring/develop Nov 11, 2026
12 of 14 checks passed
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.

1 participant