Google Git
Sign in
chromium / codesearch / chromium / src / HEAD / . / components / test / data / web_package
tree: e61897c53969b002ba6fde7f6957d64a7802f006 [path history] [tgz]
  1. hello/
  2. 24_responses.har
  3. 24_responses.wbn
  4. ecdsa_p256.pem
  5. ed25519.pem
  6. hello_b2.wbn
  7. mixed_absolute_relative_urls.har
  8. mixed_absolute_relative_urls.wbn
  9. OWNERS
  10. README.md
  11. simple.har
  12. simple_b2.wbn
  13. simple_b2_signed_v2.swbn
  14. simple_b2_signed_v2_ecdsa_p256.swbn
  15. simple_b2_signed_v2_ed25519.swbn
  16. simple_b2_signed_v2_tampered.swbn
  17. unit_tests_bundle_data.filelist
  18. unit_tests_bundle_data.globlist
components/test/data/web_package/README.md

Generating signed web bundles for testing

In general

  • wbn-sign CLI tools provide functionalities for signing the web bundles and inferring the signed web bundle ID from the key.
  • (deprecated, used prior and provided only for reference) go CLI tools were used before. They do not support signing the web bundles using v2 integrity block, so are no longer applicable.

For most of the C++ tests

EcdsaP256 signature is nondeterministic, which makes it impossible to perform at least some tests that rely on byte-wise comparison. To remediate it, WebBundleSigner for tests uses hardcoded nonce. Hence, .swbn files in this directory that are used for such tests have to be generated using this C++ code.