<?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>Https on Aperture Zone</title>
    <link>https://aperturezone.com/tags/https/</link>
    <description>Recent content in Https on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Tue, 10 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/https/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTPS on HP ProCurve V1910</title>
      <link>https://aperturezone.com/posts/procurve/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/procurve/</guid>
      <description>&lt;p&gt;Securing access to the web interface of managed switches is one of those tasks that seems trivial on paper. On recent hardware, it is indeed trivial. On HP ProCurve V1910 switches—Comware v5 switches that are still used in many home labs and small infrastructures—it&#39;s a different story. This article documents the entire project, the pitfalls, the discoveries, and an honest conclusion about what it&#39;s really worth.&lt;/p&gt;
&lt;p&gt;The test infrastructure: three HP V1910 switches (firmware 5.20 Release 1519P06) on a dedicated, isolated management VLAN with no Internet access. An internal CA based on OpenSSL runs on a Linux server in the infrastructure.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
