Consider making raw TLS over TCP based proxy

Open
#54 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
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
networking

Research direction

No files, tests, or entry points are named. Start by locating the Rust proxy server and client code, then trace HTTP header injection and TLS/TCP forwarding. Done should be defined as protocol-agnostic raw bytestream forwarding while making measurement-header injection optional.

Written by the indexing model from the issue text.

Description

discussion

This is currently an HTTP-based proxy. It could easily be made to forward raw bytestreams over TLS/TCP, but handling HTTP is needed in order to inject measurement data into the request or reponse headers. If we made the header-injection optional we could make this protocol-agnostic.

@0x416e746f6e proposed that there are cases where this would be desirable.

Dominant language
Rust
Stars
6
Forks
2
Avg merge
13m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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 flashbots/attested-tls-proxy

All issues in flashbots/attested-tls-proxy

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.