<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network Security on Amit Agarwal Linux Blog</title>
    <link>/tags/network-security/</link>
    <description>Recent content in Network Security on Amit Agarwal Linux Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 08 Feb 2025 00:00:00 +0530</lastBuildDate>
    
	<atom:link href="/tags/network-security/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Using Burp with Containers In Docker</title>
      <link>/2025/02/08/2025-02-08-UsingBurpwithContainersInDocker/</link>
      <pubDate>Sat, 08 Feb 2025 00:00:00 +0530</pubDate>
      
      <guid>/2025/02/08/2025-02-08-UsingBurpwithContainersInDocker/</guid>
      <description>&lt;h1 id=&#34;making-docker-containers-trust-burp-suites-ca-for-testing&#34;&gt;Making Docker Containers Trust Burp Suite&amp;rsquo;s CA for Testing&lt;/h1&gt;
&lt;p&gt;When testing applications running inside Docker containers, intercepting traffic with Burp Suite can be challenging because containers don’t automatically trust Burp’s CA certificate. Without trust, HTTPS requests from inside the container will fail with certificate errors.&lt;/p&gt;
&lt;p&gt;In this post, I’ll show you how to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Add Burp Suite’s CA to your host system&lt;/li&gt;
&lt;li&gt;Pass the trusted CA to Docker containers&lt;/li&gt;
&lt;li&gt;Ensure seamless HTTPS traffic interception for testing&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Let’s get started!&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
