-
Notifications
You must be signed in to change notification settings - Fork 119
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
DecoderReader accepts incorrect input #226
Comments
Good find, thanks for the heads up. |
marshallpierce
added a commit
that referenced
this issue
May 21, 2023
Fixes #226. DecoderReader now keeps more state so that erroneous internal padding that happens to fall right on a read buffer boundary isn't silently ignored.
marshallpierce
added a commit
that referenced
this issue
May 21, 2023
Fixes #226. DecoderReader now keeps more state so that erroneous internal padding that happens to fall right on a read buffer boundary isn't silently ignored.
marshallpierce
added a commit
that referenced
this issue
May 21, 2023
Fixes #226. DecoderReader now keeps more state so that erroneous internal padding that happens to fall right on a read buffer boundary isn't silently ignored.
marshallpierce
added a commit
that referenced
this issue
May 21, 2023
Fixes #226. DecoderReader now keeps more state so that erroneous internal padding that happens to fall right on a read buffer boundary isn't silently ignored.
marshallpierce
added a commit
that referenced
this issue
May 21, 2023
Fixes #226. DecoderReader now keeps more state so that erroneous internal padding that happens to fall right on a read buffer boundary isn't silently ignored.
This will be fixed in 0.21.1 momentarily. |
crapStone
pushed a commit
to Calciumdibromid/CaBr2
that referenced
this issue
Jun 12, 2023
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [base64](https://github.com/marshallpierce/rust-base64) | dependencies | patch | `0.21.0` -> `0.21.2` | --- ### Release Notes <details> <summary>marshallpierce/rust-base64</summary> ### [`v0.21.2`](https://github.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#​0212) [Compare Source](marshallpierce/rust-base64@v0.21.1...v0.21.2) - Rollback MSRV to 1.57.0 -- only dev dependencies need 1.60, not the main code ### [`v0.21.1`](https://github.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#​0211) [Compare Source](marshallpierce/rust-base64@v0.21.0...v0.21.1) - Remove the possibility of panicking during decoded length calculations - `DecoderReader` no longer sometimes erroneously ignores padding [#​226](marshallpierce/rust-base64#226) #### Breaking changes - `Engine.internal_decode` return type changed - Update MSRV to 1.60.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS45OC4wIiwidXBkYXRlZEluVmVyIjoiMzUuMTAwLjEiLCJ0YXJnZXRCcmFuY2giOiJkZXZlbG9wIn0=--> Co-authored-by: cabr2-bot <[email protected]> Reviewed-on: https://codeberg.org/Calciumdibromid/CaBr2/pulls/1907 Reviewed-by: crapStone <[email protected]> Co-authored-by: Calciumdibromid Bot <[email protected]> Co-committed-by: Calciumdibromid Bot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When parts read from underlying reader include valid padding the
reader accepts the input even if there’s more data to follow. In this
example the reader produces string
AA==AA==AA==
which should resultin an error but instead generates three zero bytes.
The text was updated successfully, but these errors were encountered: