Google Git
Sign in
chromium / chromiumos / platform / redaction_tool / refs/heads/release-R122-15753.B
commitbe9d6c72959142f6771e0e2ffad1bcf36a76d9d8[log] [tgz]
authorMatthias Kaehlcke <[email protected]>Tue Dec 19 16:21:29 2023
committerChromeos LUCI <[email protected]>Fri Dec 22 04:18:39 2023
treef82cc2d63a215600839d126d3eef2118fc39d9c1
parent55ec79ce4afc543a9e50b18a9a1f4fd00b81353d [diff]
redaction_tool: Redact partial user id hashes from cryptohome device names

The name of Cryptohome storage devices include a partial hash
of the user id, e.g.:

  dmcrypt-0d9a4e74-data
  E7341N6FNEYIR2CX-cryptohome--0d9a4e74--data

Redact these partial hashes.

cherry-pick of https://crrev.com/c/5124299. Not a merge because
re2 uprev still seems to be pending.

BUG=b:309001479
TEST=FEATURES=test emerge-${BOARD} redaction_tool

Change-Id: I23093f47bc082a04a65d97d28da2049f928a322e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/5147076
Tested-by: Matthias Kaehlcke <[email protected]>
Reviewed-by: Ian Barkley-Yeung <[email protected]>
Commit-Queue: Matthias Kaehlcke <[email protected]>
2 files changed
tree: f82cc2d63a215600839d126d3eef2118fc39d9c1
  1. BUILD.gn
  2. DIR_METADATA
  3. ip_address.cc
  4. ip_address.h
  5. libmetrics_metrics_recorder.cc
  6. libmetrics_metrics_recorder.h
  7. libmetrics_metrics_tester.cc
  8. libmetrics_metrics_tester.h
  9. metrics_tester.h
  10. OWNERS
  11. pii_types.h
  12. PRESUBMIT.cfg
  13. README.md
  14. redaction_tool.cc
  15. redaction_tool.h
  16. redaction_tool_metrics_recorder.h
  17. redaction_tool_unittest.cc
  18. url_canon.h
  19. url_canon_internal.cc
  20. url_canon_internal.h
  21. url_canon_ip.cc
  22. url_canon_ip.h
  23. url_canon_stdstring.cc
  24. url_canon_stdstring.h
  25. url_parse.h
  26. validation.cc
  27. validation.h
README.md

redaction_tool: PII Redaction Tool

A redaction_tool redacts PII using a wide set of RegEx expressions.

This code is a mirror of https://source.chromium.org/chromium/chromium/src/+/main:components/feedback/redaction_tool/

Changes should be made in chromium code base only and then be upreved here.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update
  • git checkout -b main cros/main
  • git merge cros/upstream/main
    • BUILD.gn should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/feedback”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.
  • Push the resulting merge commit for review with:
    • git push HEAD:refs/for/main