<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: mhils</title><link>https://news.ycombinator.com/user?id=mhils</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 16 Nov 2026 00:55:26 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mhils" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by mhils in "PyPI's redesigned project pages with clearer security signals are now live"]]></title><description><![CDATA[
<p>Very cool to see PyPI put more emphasis towards exposing provenance info. It would be even cooler if trusted publishing would finally support reusable workflows (<a href="https://github.com/pypi/warehouse/issues/11096" rel="nofollow">https://github.com/pypi/warehouse/issues/11096</a>).</p>
]]></description><pubDate>Sat, 14 Nov 2026 16:55:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=50498514</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=50498514</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50498514</guid></item><item><title><![CDATA[New comment by mhils in "mitmproxy adds --emudhra option"]]></title><description><![CDATA[
<p>I think the term compromised is ok here: "made vulnerable (as to attack or misuse) by unauthorized access, revelation, or exposure" (<a href="https://www.merriam-webster.com/dictionary/compromised" rel="nofollow">https://www.merriam-webster.com/dictionary/compromised</a>).</p>
]]></description><pubDate>Thu, 22 Oct 2026 12:47:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=50194610</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=50194610</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50194610</guid></item><item><title><![CDATA[New comment by mhils in "mitmproxy adds --emudhra option"]]></title><description><![CDATA[
<p>Ha, I didn't expect this to show up on HN!<p>Release is out now, including a blog post at <a href="https://www.mitmproxy.org/posts/releases/mitmproxy-12.3/" rel="nofollow">https://www.mitmproxy.org/posts/releases/mitmproxy-12.3/</a>. There isn't really much to explain, you just pass `--emudhra`. :)</p>
]]></description><pubDate>Thu, 22 Oct 2026 02:29:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=50190448</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=50190448</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50190448</guid></item><item><title><![CDATA[New comment by mhils in "mitmproxy adds --emudhra option"]]></title><description><![CDATA[
<p>I didn't expect this commit to end up on HN, otherwise I would have done the full integration in one go. :) <a href="https://github.com/mitmproxy/mitmproxy/pull/8503" rel="nofollow">https://github.com/mitmproxy/mitmproxy/pull/8503</a> adds the AAA root path.</p>
]]></description><pubDate>Thu, 22 Oct 2026 02:18:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=50190362</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=50190362</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50190362</guid></item><item><title><![CDATA[New comment by mhils in "Gemini 4 Argon"]]></title><description><![CDATA[
<p>> Has there been progress in improving that aspect during the LLM phase of the rewrite?<p>I'd say so! We aim to have our replacements to be `forbid(unsafe)` - no raw pointers - outside of `ffi.rs`. Of course it's tricky because we need to interoperate with existing C code, but we've been trying to come up with abstractions that make this a bit more ergonomic (<a href="https://github.com/google/safer_cffi" rel="nofollow">https://github.com/google/safer_cffi</a>).</p>
]]></description><pubDate>Thu, 01 Oct 2026 09:20:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=49919531</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=49919531</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49919531</guid></item><item><title><![CDATA[New comment by mhils in "Scaling Memory Safety: AI-Assisted Rewrites of C/C++ Dependencies to Rust"]]></title><description><![CDATA[
<p>> didn't say they did anything with a VLM to check the output vs the original library<p>Assuming VLM stands for vision–language model: We validated that all pixels are bit-identical across those 30M GIFs. So we didn't need a language model for that, we just compared expected and actual pixel buffers for strict equality. :)</p>
]]></description><pubDate>Wed, 30 Sep 2026 23:57:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=49916016</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=49916016</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49916016</guid></item><item><title><![CDATA[New comment by mhils in "Gemini 4 Argon"]]></title><description><![CDATA[
<p>There is a blog post on (the early baby steps of) that: <a href="https://bughunters.google.com/blog/scaling-memory-safety" rel="nofollow">https://bughunters.google.com/blog/scaling-memory-safety</a>. We have multiple AI-assisted Rust rewrites running in production now.<p>(Full disclosure: I am one of the coauthors)</p>
]]></description><pubDate>Wed, 30 Sep 2026 21:30:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=49914748</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=49914748</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49914748</guid></item><item><title><![CDATA[New comment by mhils in "Pdoc – Generate API documentation for Python projects"]]></title><description><![CDATA[
<p>FWIW I agree that the Rust way is nicer, but I can't impose the Rust way on Python. I guess the secret hack is to use PyO3, which pdoc supports quite well. ;)</p>
]]></description><pubDate>Tue, 07 Oct 2025 17:08:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=45505807</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=45505807</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45505807</guid></item><item><title><![CDATA[New comment by mhils in "Pdoc – Generate API documentation for Python projects"]]></title><description><![CDATA[
<p>pdoc3 is not pdoc, see <a href="https://github.com/mitmproxy/pdoc?tab=readme-ov-file#pdoc-vs-pdoc3" rel="nofollow">https://github.com/mitmproxy/pdoc?tab=readme-ov-file#pdoc-vs...</a>.</p>
]]></description><pubDate>Tue, 07 Oct 2025 17:06:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=45505775</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=45505775</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45505775</guid></item><item><title><![CDATA[New comment by mhils in "Pdoc – Generate API documentation for Python projects"]]></title><description><![CDATA[
<p>Let me try to explain why it is that way: First, it's consistent with Python functions. The docstring for functions is below the signature as well. Second, consider a file with only a docstring and then a variable declaration. Here it would be ambiguous if that's the module or the variable docstring. Finally, this behavior is consistent with other tools (and failed standardization efforts) in the space. So yeah - I share your sentiment, but I think it's the most pragmatic approach for pdoc. :)</p>
]]></description><pubDate>Tue, 07 Oct 2025 09:08:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=45500951</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=45500951</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45500951</guid></item><item><title><![CDATA[New comment by mhils in "Pdoc – Generate API documentation for Python projects"]]></title><description><![CDATA[
<p>pdoc maintainer here. Pleasant surprise to see us on HN again, and happy to answer any questions! :)</p>
]]></description><pubDate>Tue, 07 Oct 2025 08:54:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=45500864</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=45500864</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45500864</guid></item><item><title><![CDATA[New comment by mhils in "Pdoc – Generate API documentation for Python projects"]]></title><description><![CDATA[
<p>I'd say neither fork as made great strides since then, but I'm also biased here as the maintainer of pdoc.<p>There is no pdoc-specific library for link checking as far as I'm aware. It's all plain HTML though, so you can use a more general tool like <a href="https://lychee.cli.rs/" rel="nofollow">https://lychee.cli.rs/</a>. :)</p>
]]></description><pubDate>Tue, 07 Oct 2025 08:34:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=45500741</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=45500741</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45500741</guid></item><item><title><![CDATA[New comment by mhils in "Show HN: Subtrace – Wireshark for Docker Containers"]]></title><description><![CDATA[
<p>Congrats on the seccomp-based interception, that's a really neat way to solve this problem! We did some BPF_PROG_TYPE_CGROUP_SOCK eBPF shenanigans in mitmproxy for redirection, but that doesn't work with containers at all. Cool to see that intercepting all relevant syscalls works that well.</p>
]]></description><pubDate>Thu, 20 Feb 2025 14:12:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=43114840</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=43114840</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43114840</guid></item><item><title><![CDATA[New comment by mhils in "Httptap: View HTTP/HTTPS requests made by any Linux program"]]></title><description><![CDATA[
<p>This is really cool, thank you for sharing! We've built a similar feature for mitmproxy lately, but with different tradeoffs. Our approach does require root and we don't have automated certificate install (yet), but we don't require apps to run in a dedicated namespace (so you can capture already-running processes). Super awesome to see this now, excited to dive into the code and see how you do TCP reassembly etc. :)</p>
]]></description><pubDate>Mon, 03 Feb 2025 22:11:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=42923987</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=42923987</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42923987</guid></item><item><title><![CDATA[New comment by mhils in "Httptap: View HTTP/HTTPS requests made by any Linux program"]]></title><description><![CDATA[
<p>> so you have to configure your program to use a proxy server.<p>That's not true for local capture mode: <a href="https://mitmproxy.org/posts/local-capture/linux/" rel="nofollow">https://mitmproxy.org/posts/local-capture/linux/</a>. :)</p>
]]></description><pubDate>Mon, 03 Feb 2025 22:03:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=42923884</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=42923884</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42923884</guid></item><item><title><![CDATA[New comment by mhils in "PyPI now supports digital attestations"]]></title><description><![CDATA[
<p>Fully reproducible builds would of course be nicer from a security standpoint, but attestations have vastly lower implementation costs and scale much better while still raising the bar meaningfully.</p>
]]></description><pubDate>Fri, 15 Nov 2024 14:42:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=42147338</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=42147338</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42147338</guid></item><item><title><![CDATA[New comment by mhils in "Mitmproxy 11: Full HTTP/3 Support"]]></title><description><![CDATA[
<p>One of the main promises of HTTP/3 is better performance under worse network conditions (e.g. no head-of-line blocking as in HTTP/2, connection migration, 0-RTT). For all of that HTTP/3 between client and proxy is really great. HTTP/3 between proxy and server is not required for that.</p>
]]></description><pubDate>Sat, 05 Oct 2024 03:45:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=41747572</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=41747572</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41747572</guid></item><item><title><![CDATA[New comment by mhils in "Mitmproxy 11: Full HTTP/3 Support"]]></title><description><![CDATA[
<p>Thank you for your work on Hickory! It's super exciting to see how PyO3's Python <-> Rust interop enables us to use a production-grade DNS library with Hickory and also a really solid user-space networking stack with smoltcp. These things wouldn't be available in Python otherwise.</p>
]]></description><pubDate>Sat, 05 Oct 2024 03:37:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=41747534</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=41747534</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41747534</guid></item><item><title><![CDATA[Mitmproxy 11: Full HTTP/3 Support]]></title><description><![CDATA[
<p>Article URL: <a href="https://mitmproxy.org/posts/releases/mitmproxy-11/">https://mitmproxy.org/posts/releases/mitmproxy-11/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=41744434">https://news.ycombinator.com/item?id=41744434</a></p>
<p>Points: 388</p>
<p># Comments: 75</p>
]]></description><pubDate>Fri, 04 Oct 2024 18:52:46 +0000</pubDate><link>https://mitmproxy.org/posts/releases/mitmproxy-11/</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=41744434</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41744434</guid></item><item><title><![CDATA[New comment by mhils in "Intent to end OCSP service"]]></title><description><![CDATA[
<p>There's OCSP Must-Staple, which makes MITM without stapling impossible. That is, if the client implements it and does not fail open. :)</p>
]]></description><pubDate>Tue, 23 Jul 2024 20:56:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=41050738</link><dc:creator>mhils</dc:creator><comments>https://news.ycombinator.com/item?id=41050738</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41050738</guid></item></channel></rss>