https://www.blog-des-telecoms.com/tags/release/Recent content in Release on Mathias WOLFFHugofr-FR<a href="https://www.blog-des-telecoms.com">Blog des télécoms</a> © 2009 - 2026 by <a href="https://www.linkedin.com/in/mathias-wolff-47a7941/">Mathias WOLFF</a> is licensed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0</a><img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;">Fri, 19 Jun 2026 07:10:30 +0200https://www.blog-des-telecoms.com/en/blog/pi-secured-setup-v1-0-1-v1-0-2-security-hardening/Thu, 18 Jun 2026 18:30:00 +0200https://www.blog-des-telecoms.com/en/blog/pi-secured-setup-v1-0-1-v1-0-2-security-hardening/<p>Two releases on the same day, twenty minutes apart: <strong>v1.0.1</strong> then <strong>v1.0.2</strong>. Both do the same job — harden pi-secured-setup itself. This is a short post to explain what changed and why it matters, because a security tool that ships its own vulnerabilities loses all credibility.</p> <p>If you&rsquo;re new to the project, <a href="https://www.blog-des-telecoms.com/en/blog/securing-pi-from-the-inside-guards-scanners-audit/" >the introductory article</a> covers the basics: Guards, Scanners, the audit trail.</p> <h2 id="v101--the-quality-pass">v1.0.1 — the quality pass<a href="#v101--the-quality-pass" class="post-heading__anchor" aria-hidden="true">#</a> </h2> <p>Three threads:</p>https://www.blog-des-telecoms.com/blog/pi-secured-setup-v1-0-1-v1-0-2-durcissement-securite/Thu, 18 Jun 2026 18:30:00 +0200https://www.blog-des-telecoms.com/blog/pi-secured-setup-v1-0-1-v1-0-2-durcissement-securite/<p>Deux releases le même jour, à vingt minutes d&rsquo;intervalle : <strong>v1.0.1</strong> puis <strong>v1.0.2</strong>. Les deux font le même travail — durcir pi-secured-setup lui-même. C&rsquo;est un billet court pour expliquer ce qui a changé et pourquoi ça compte, parce qu&rsquo;un outil de sécurité qui traîne ses propres vulnérabilités perd toute crédibilité.</p> <p>Si vous découvrez le projet, <a href="https://www.blog-des-telecoms.com/blog/securiser-pi-de-l-interieur-guards-scanners-audit/" >l&rsquo;article de présentation</a> pose les bases : Guards, Scanners, audit trail.</p> <h2 id="v101--amélioration-qualité">v1.0.1 — amélioration qualité<a href="#v101--am%c3%a9lioration-qualit%c3%a9" class="post-heading__anchor" aria-hidden="true">#</a> </h2> <p>Trois axes :</p>