)]}'
{
  "commit": "434c4c0b1d32a5462499c0a1006c785b4a766bb6",
  "tree": "90b39dbf16c09a27776730e1a5d27a5c7bd2e90c",
  "parents": [
    "d5e8c8e71d9e2bd70157750e6ac432663c46d8f8"
  ],
  "author": {
    "name": "QUICHE team",
    "email": "quiche-dev@google.com",
    "time": "Thu Sep 10 07:27:56 2020 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Sep 10 07:28:27 2020 -0700"
  },
  "message": "Self-instrument for QUIC library via setsockopt for on-host-monitoring.\n\ngo/secure-protocols-on-host-detection is our design to implement\non-host monitoring for connection tracking. It requires code creating\nsockets to tag the socket through an additional syscall. Most of our\ntraffic is covered through Stubby, but Quic also generates a lot of\ntraffic and manages raw sockets itself.\n\nThis CL should close the monitoring gap for Quic.\n\nGiven that we already do setsockopt tagging inside Stubby2 and GRPC (which the GFE uses), we chose not to flag protect this code path, as this is basically a tested feature at this point. Please see CL Discussion.\n\ngfe-relnote: Self-instrument for QUIC library via setsockopt for on-host-monitoring.\nPiperOrigin-RevId: 330932821\nChange-Id: Ibf83cbdbe6792119b83e702e0f702b22bcb6253d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c5ab345f433934658ab4c2ecf7bb0f83ea43c81e",
      "old_mode": 33188,
      "old_path": "quic/core/quic_udp_socket_posix.cc",
      "new_id": "ea68727211cbacb3933f999b14945f59ac44cc4f",
      "new_mode": 33188,
      "new_path": "quic/core/quic_udp_socket_posix.cc"
    },
    {
      "type": "modify",
      "old_id": "2b1f9c3fbc5518bc8cd02fbe008884c439220f99",
      "old_mode": 33188,
      "old_path": "quic/platform/api/quic_udp_socket_platform_api.h",
      "new_id": "10307efc29875a46bea1657510ad993332ec8c22",
      "new_mode": 33188,
      "new_path": "quic/platform/api/quic_udp_socket_platform_api.h"
    }
  ]
}
