Support for MITM

Open
#41 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
networking, security

Research direction

No files or tests are named. Start by locating tokenizer's HTTP proxy and HTTPS/TLS entry points, then determine the design needed to intercept HTTPS for applications that trust an installed self-signed certificate. Done should include MITM support for non-pinned certificates while preserving the stated limitation for certificate-pinned applications.

Written by the indexing model from the issue text.

Description

Any plans to add support for MITM here?

The use case is the scenario of the deployer running an application they don't control. DNS would then be modified to reroute requests to tokenizer without the application being aware of this. Many applications in the scenario would be using HTTPS and so tokenizer would need to serve a self signed cert that could be installed into the trust store of the OS where the application is running. This doesn't solve for applications that require certificate pinning, but would still address most scenarios as I don't think certificate pinning is common in backend tools.

Dominant language
Go
Stars
494
Forks
20
Avg merge
5d 6h
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 superfly/tokenizer

All issues in superfly/tokenizer

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.