<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on PodVader</title><link>https://podvader.com/posts/</link><description>Recent content in Posts on PodVader</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 09 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://podvader.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Signed Git Commits. Why and How</title><link>https://podvader.com/posts/signed-git-commits.-why-and-how/</link><pubDate>Sat, 09 Mar 2024 00:00:00 +0000</pubDate><guid>https://podvader.com/posts/signed-git-commits.-why-and-how/</guid><description>&lt;p&gt;Signed Git commits offer an extra layer of security in the development process. By digitally signing your commits, you and others can verify the authenticity, integrity, and origin of the code changes.&lt;/p&gt;
&lt;p&gt;We will explore what signed Git commits are, why you want them signed and how to actually sign commits.&lt;/p&gt;
&lt;h1 id="why-sign-commits"&gt;
 Why Sign Commits?
 &lt;a class="heading-link" href="#why-sign-commits"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;When working in a team, anyone with sufficient permissions can push code to a repository. While it is true that you&amp;rsquo;d need to be authenticated while doing so, this does not guarantee that the pushed commits were generated by the person pushing them. Anyone could just change their &lt;code&gt;user.name&lt;/code&gt; and &lt;code&gt;user.email&lt;/code&gt; to match yours and commit code with abysmal variable names, effectively impersonating you.&lt;/p&gt;</description></item></channel></rss>