<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SSL on BrainBit Latest Articles</title><link>https://brainbit.uk/tags/ssl/</link><description>Recent content in SSL on BrainBit Latest Articles</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 02 Nov 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://brainbit.uk/tags/ssl/index.xml" rel="self" type="application/rss+xml"/><item><title>Packet Where Are You?</title><link>https://brainbit.uk/posts/pwru/</link><pubDate>Tue, 02 Nov 2021 00:00:00 +0000</pubDate><guid>https://brainbit.uk/posts/pwru/</guid><description>PWRU (Packet Where Are you) Taken from the their github repo https://github.com/cilium/pwru : &amp;ldquo;pwru is an eBPF-based tool for tracing network packets in the Linux kernel with advanced filtering capabilities. It allows fine-grained introspection of kernel state to facilitate debugging network connectivity issues.&amp;rdquo;
So it is a tool that attach a bunch of kprobes to specific kernel functions or interfaces I&amp;rsquo;m not so sure and it shows places in the kernel data path that a given packet traverses</description></item><item><title>Cilium TLS inspection</title><link>https://brainbit.uk/posts/cilium-tls-inspection/</link><pubDate>Sat, 11 Sep 2021 00:00:00 +0100</pubDate><guid>https://brainbit.uk/posts/cilium-tls-inspection/</guid><description>TLS in simple terms When your browser verifies a TLS certificate , it checks for expiration , domains , sans etc&amp;hellip; but the most important thing it does is it verifies that the certificate has been signed by a CA (Certificate Authority ) it (the browser) trusts. These CAs are a bunch of arbitrary organisations that are allowed to sign certificate requests etc.
A self-signed certificate , in general terms , is as valid as a certificate singed by a CA , the main difference is that is not signed by a CA that is trusted by the browser.</description></item><item><title>Vault as CA with PKI backend</title><link>https://brainbit.uk/posts/vault-as-ca-with-pki-backend/</link><pubDate>Sun, 29 Oct 2017 14:47:58 +0000</pubDate><guid>https://brainbit.uk/posts/vault-as-ca-with-pki-backend/</guid><description>I’m gonna show how to run your own CA within pki framework , and be able to generate private keys and sign certificates. We will do this with vault , just because it’s the fastest way to get it done.
Download and run Vault: Make sure you get it from https://www.vaultproject.io/downloads.html or you build it by hand whatever you prefer.
We will run this in development mode for this tutorial but make sure you do something better if you’re running this in production.</description></item></channel></rss>