Google Git
Sign in
chromium / chromiumos / platform / redaction_tool / c54d7196be12b917395dc77424936c070adfa0fd
commitc54d7196be12b917395dc77424936c070adfa0fd[log] [tgz]
authorDonna Dionne <donnadionne@google.com>Mon Feb 19 08:24:50 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Feb 22 18:14:00 2024
tree7a18508f6b47cedf5769f8650869d8550ec5df9d
parent84107932fbd44e3a5135979afdfe5460cb8a9700 [diff]
redaction_tool: keeping the source up-to-date (memory dumps) The redaction tool can now redact GSC dev ids, serial, and memory dumps. BUG=b:286427956 TEST=cros_workon_make --board=${BOARD} crash-reporter --test Change-Id: I06aaedbde2f589a0aea4dbc1865a2a051f6747ff Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/5306001 Reviewed-by: Xiangdong Kong <xiangdongkong@google.com> Tested-by: Donna Dionne <donnadionne@google.com> Commit-Queue: Donna Dionne <donnadionne@google.com> Reviewed-by: Ian Barkley-Yeung <iby@chromium.org>
3 files changed
tree: 7a18508f6b47cedf5769f8650869d8550ec5df9d
  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