Skip to content

fix(aes-ctr): validate browser counter lengths - #395

Open
harrshita123 wants to merge 1 commit into
google:masterfrom
harrshita123:fix/aes-ctr-counter-length-validation
Open

harrshita123 wants to merge 1 commit into
google:masterfrom
harrshita123:fix/aes-ctr-counter-length-validation

Conversation

@harrshita123

Copy link
Copy Markdown
Contributor

Summary

  • validate AES-CTR counter bit lengths before browser interop
  • align browser errors with the native backend
  • add cross-backend regression coverage for invalid lengths

Fixes #392

Testing

  • dart analyze --fatal-warnings
  • dart test -p vm
  • dart test -p chrome test/webcrypto_test.dart
  • dart test -p chrome --compiler dart2wasm test/webcrypto_test.dart

This branch has not been deployed

No deployments
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.

bug: browser AES-CTR exposes inconsistent errors for invalid counter bit lengths

1 participant