After this split, automation will be able to update the pins list in
Chrome from the source of truth in the internal repo (as it does for
the .pins file). This change only affects the code used to generate the
trie. Once Chrome is compiled, the behavior is exactly the same as
before.
For the most part this change is a no-op, with the exception of how
include_subdomains is treated. Previously, include_subdomains affected
both HSTS and KP, while include_subdomains_for_pinning affected only
KP. With this change, include_subdomains_for_pinning was removed, and
the json files have separate include_subdomains fields which apply only
for HSTS and KP respectively.
As part of the migration to the separate list, subdomains that had
either include_subdomains or include_subdomains_for_pinning set were
added with include_subdomains in the new pins.json list, so the new
lists are equivalent in behavior to the old ones.
Bug: 1286121
Change-Id: Ib6cd7740b96909051f73f93f25cf50fbf51be63a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4093098
Commit-Queue: Carlos IL <carlosil@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1084094}