<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Curl on Junian Dev</title><link>https://www.junian.dev/tags/curl/</link><description>Recent content in Curl on Junian Dev</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><managingEditor>author@junian.dev (Junian Triajianto)</managingEditor><webMaster>author@junian.dev (Junian Triajianto)</webMaster><copyright>Copyright &amp;copy; 2014 - 2026 &lt;a href='https://www.junian.dev/'&gt;Junian.dev&lt;/a&gt;</copyright><lastBuildDate>Fri, 23 Oct 2026 04:00:00 +0700</lastBuildDate><atom:link href="https://www.junian.dev/tags/curl/index.xml" rel="self" type="application/rss+xml"/><item><title>Using git on Mac with Custom Certificate - eMudhra CA Fix</title><link>https://www.junian.dev/blog/mac-git-custom-ca-cert/</link><pubDate>Fri, 23 Oct 2026 04:00:00 +0700</pubDate><author>author@junian.dev (Junian Triajianto)</author><guid>https://www.junian.dev/blog/mac-git-custom-ca-cert/</guid><description>&lt;p&gt;Previously, I wrote about a temporary fix by &lt;a href="https://www.junian.dev/blog/mac-curl-custom-ca-cert/"&gt;making the built-in &lt;code&gt;curl&lt;/code&gt; on macOS to use a custom CA bundle&lt;/a&gt; after the eMudhra incident.
But &lt;code&gt;curl&lt;/code&gt; is not the only tool in my terminal that talks to the internet.
&lt;code&gt;git&lt;/code&gt; does too, especially when I push and pull over HTTPS.&lt;/p&gt;
&lt;p&gt;It turns out the system &lt;code&gt;git&lt;/code&gt; has the same problem.
By default, it still uses the CA file from &lt;code&gt;/etc/ssl/cert.pem&lt;/code&gt;, the same file that still trusts the compromised eMudhra CA (by the time I published this article).&lt;/p&gt;</description></item><item><title>Using cURL on Mac with Custom Certificate - eMudhra CA Fix</title><link>https://www.junian.dev/blog/mac-curl-custom-ca-cert/</link><pubDate>Thu, 22 Oct 2026 04:00:00 +0700</pubDate><author>author@junian.dev (Junian Triajianto)</author><guid>https://www.junian.dev/blog/mac-curl-custom-ca-cert/</guid><description>&lt;p&gt;At the time I wrote this article, there was an incident of a private key compromised by a Certificate Authority, eMudhra.
What does that mean for us?&lt;/p&gt;
&lt;p&gt;Well, as long as this CA is trusted, anyone can just generate a valid certificate as they wish and can decrypt HTTPS traffic.
Meaning they could do a MITM attack without you realizing it.&lt;/p&gt;
&lt;p&gt;After the eMudhra incident, most browsers and apps already made an update so this CA is no longer trusted.
If you haven&amp;rsquo;t yet, you should update everything now.&lt;/p&gt;</description></item></channel></rss>