RSrs_rs_rs_rs_rs·Aug 27, 2023
Not a CF employee but I am pretty sure it's working as intended as they built and use this:
https://github.com/cloudflare/mitmengine
In Block YouTube ads on AppleTV by decrypting and stripping ads from Profobufcloudflare
mitmengine
Go2019–2023
cloudflare / mitmengine · Archived
mitmengine
A MITM (monster-in-the-middle) detection tool. Used to build MALCOLM:
3Distinct people
3Mentions
0Explicit recommenders
810GitHub stars
What to know before exploring
What it is
A MITM (monster-in-the-middle) detection tool. Used to build MALCOLM:
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year3 dated mentions
Observed mentions: 2019-08-12 13:23:44 UTC to 2023-08-27 06:15:14 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesNo one here is objecting to it as a standalone phrase, but as a replacement for a perfectly good phrase that existed all ready. There is no reason to change existing terminology and cause confusion; who decided this was a problem, any way? It reminds me of Bro being renamed to "zeek" because of the whole "brogrammer" thing, even though it was named before any one ever started complaining about that after Big Brother. It's not a real issue. I wouldn't have a serious problem with it, except that some one who wants to learn more is now stuck searching for one of the three other people who decided this was an actual issue and used it instead of MITM. Again, same as with Bro: now you have to search for two terms, even if you're familiar with the distinction. I can find posts going back to the 90s on Bro; "zeek" has very little in compari
Read the rest
son.
It turns out even cloud flare used man-in-the-middle in the project, because it was in some other code, I guess: https://github.com/cloudflare/mitmengine/blob/master/process...
(line 24; now wait for some one to realize his "error" and change it.)
I have seen it in at least one other project: https://blog.cloudflare.com/monsters-in-the-middleboxes/, https://github.com/cloudflare/mitmengine
I think it's equally understandable, and monster is objectively a more fun word. Seems like not a big deal?
In Spying on HTTPS