<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Daniel Corneschi</title><link>https://blog.corneschi.ro/tags/security/</link><description>Recent content in Security on Daniel Corneschi</description><generator>Hugo</generator><language>en</language><copyright>Daniel Corneschi</copyright><lastBuildDate>Wed, 07 Oct 2026 23:47:29 +0300</lastBuildDate><atom:link href="https://blog.corneschi.ro/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform Lock File Checksums: zh and h1 Hashes</title><link>https://blog.corneschi.ro/posts/terraform-lock-file-checksums/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.corneschi.ro/posts/terraform-lock-file-checksums/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;&#10;&lt;p&gt;The &lt;code&gt;.terraform.lock.hcl&lt;/code&gt; file stores cryptographic hashes that verify the integrity of downloaded providers. Two hash schemes exist: &lt;code&gt;zh:&lt;/code&gt; (a legacy scheme tied to zip archives) and &lt;code&gt;h1:&lt;/code&gt; (a directory hash of the unpacked provider). Understanding how these are calculated helps when debugging lock file mismatches or verifying providers manually.&lt;/p&gt;&#10;&lt;h2 id="zh-and-h1-checksums"&gt;zh and h1 Checksums&lt;/h2&gt;&#10;&lt;p&gt;The &lt;code&gt;terraform init&lt;/code&gt; command downloads the provider and verifies that it matches one of the checksums in the lock file, then extracts the package into &lt;code&gt;.terraform/providers&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>