This website uses cookies
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services.
Consent Selection
Details
  • Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
  • Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
    • We do not use cookies of this type.

  • Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
    • We do not use cookies of this type.

  • Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
    • We do not use cookies of this type.

  • Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
    • __emg_sidPending
      Maximum Storage Duration: 1 dayType: HTTP Cookie
      __emg_vidPending
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      nl-read-countPending
      Maximum Storage Duration: PersistentType: HTML Local Storage
Cookie declaration last updated on 8/12/26 by Cookiebot
[#IABV2_TITLE#]
[#IABV2_BODY_INTRO#]
[#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#]
[#IABV2_BODY_PREFERENCE_INTRO#]
[#IABV2_BODY_PURPOSES_INTRO#]
[#IABV2_BODY_PURPOSES#]
[#IABV2_BODY_FEATURES_INTRO#]
[#IABV2_BODY_FEATURES#]
[#IABV2_BODY_PARTNERS_INTRO#]
[#IABV2_BODY_PARTNERS#]
About
Cookies are small text files that can be used by websites to make a user's experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission.

This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages.

You can at any time change or withdraw your consent from the Cookie Declaration on our website.

Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy.

Please state your consent ID and date when you contact us regarding your consent.
NewsLayer.com

Mutual Post-Quantum Auth over IKEv2 – IPsec Series, Part 8

Cisco Blogs’ eighth installment in its IPsec series focuses on mutual post-quantum authentication over IKEv2. The excerpt identifies the topic and series placement but provides no further technical details.

Cisco Blogs

Publisher

Aug 24, 2026 at 7:43 PM UTC · Updated 8 saat önce · 7 dk okuma

Mutual Post-Quantum Auth over IKEv2 – IPsec Series, Part 8
Image via Cisco Blogs

Key Signal

6 fragments ML-DSA handshake limit

Last Updated

8 saat önce

Çevriliyor…

Öne Çıkanlar

  • The article is part 8 of an IPsec-focused series.
  • Its stated topic is mutual post-quantum authentication over IKEv2.
  • The article is published on Cisco Blogs.

In Part 7 we minted post-quantum certificates and weighed them. But certificates sitting in a folder are only half the fun. Time to do the job they were born for: prove identity. We’ll stand up two containers, each holding a certificate, and watch them prove who they are to each other before the tunnel comes up. That’s mutual authentication, over a real IKEv2 handshake.

And we’ll do it twice, and the progression is the whole point:

  1. Classical ECDSA (today’s real-world posture), on stable strongSwan.
  2. Post-quantum ML-DSA (the bleeding edge), on an experimental branch.

This Part uses the authentication/ lab: its own little stack, separate from the key-exchange one. Only Docker required.


Clone the repo

Grab the repo and step into this lab’s directory. All commands below run from ipsec/authentication/:

git clone https://github.com/juliogomez/pqc.git
cd ipsec/pqc/authentication

How the trust works

Both peers trust one tiny Certificate Authority we spin up just for the lab. The CA signs two leaf certificates (one per peer), and each peer gets the CA cert pre-installed so it can verify the other side. During the handshake each peer sends only its own leaf cert; the CA is already known to both. (That keeps the on-the-wire bytes down, which matters a lot once the certs go post-quantum, as Part 7 showed so clearly.) A helper script, gen-certs.sh, does all the minting; you just tell it which algorithm to use.