Security of tracing headers in GRPC metadata

Open
#944 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, grpc
Domain
distributed-systems, security

Research direction

Start by locating the tracing framework and the gRPC metadata propagation path in the repository. Review how correlation data is handled across services and determine what security risks or protections apply. Done means the security implications are documented clearly and any required follow-up is identified.

Written by the indexing model from the issue text.

Description

The tracing framework uses GRPC metadata to propagate correlation data across services. How does this affect security?

cc @kostko

Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oasisprotocol/oasis-core

All issues in oasisprotocol/oasis-core

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.