<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Protobuf on Dhiru's Notebook</title><link>https://rfcorner.in/tags/protobuf/</link><description>Recent content in Protobuf on Dhiru's Notebook</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 16 Apr 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://rfcorner.in/tags/protobuf/index.xml" rel="self" type="application/rss+xml"/><item><title>Debugging/Reversing Firebase gRPC Traffic with mitmproxy</title><link>https://rfcorner.in/posts/debugging-grpc-traffic-with-mitmproxy/</link><pubDate>Wed, 16 Apr 2025 00:00:00 +0000</pubDate><guid>https://rfcorner.in/posts/debugging-grpc-traffic-with-mitmproxy/</guid><description>&lt;p&gt;Recently, I was stuck trying to understand how Firebase gRPC calls worked and
how I could generate, modify, and replay them. Trapping and modifying existing
gRPC traffic was not working well. Finally, I took a step back and spent some
time learning how to build and debug simple Firebase applications. This
approach helped me tremendously, and I was able to make further progress with
my original task quickly.&lt;/p&gt;
&lt;h2 id="solution"&gt;Solution&lt;/h2&gt;
&lt;p&gt;You may find the following code sample useful when reversing/debugging Firebase
applications.&lt;/p&gt;</description></item></channel></rss>