<?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>Git on Moises Vega</title><link>https://mvega.dev/tags/git/</link><description>Recent content in Git on Moises Vega</description><generator>Hugo</generator><language>en-us</language><copyright>Moises Vega</copyright><lastBuildDate>Fri, 14 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mvega.dev/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Signing Git Commits with SSH Keys</title><link>https://mvega.dev/posts/ssh-commit-signing/</link><pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate><guid>https://mvega.dev/posts/ssh-commit-signing/</guid><description>&lt;p&gt;Git identity is self-declared. &lt;code&gt;user.email&lt;/code&gt; is a config value, not a
credential — anyone can set it to your address, commit, and push
wherever they have write access. GitHub renders your avatar on the
result. Nothing in the process verifies that you wrote anything.&lt;/p&gt;
&lt;p&gt;Commit signing fixes that, and since Git 2.34 you can do it with the
SSH key you already push with. No GPG keyring, no key servers, no
expiry dance.&lt;/p&gt;</description></item></channel></rss>