<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Ke's Notes and Blogs</title><link>https://kxue43.github.io/notes-and-blogs/tags/git/</link><description>Recent content in Git on Ke's Notes and Blogs</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 05 Nov 2024 21:38:04 -0500</lastBuildDate><atom:link href="https://kxue43.github.io/notes-and-blogs/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>GPG for GitHub</title><link>https://kxue43.github.io/notes-and-blogs/notes/gpg-for-github/</link><pubDate>Tue, 05 Nov 2024 21:38:04 -0500</pubDate><guid>https://kxue43.github.io/notes-and-blogs/notes/gpg-for-github/</guid><description>&lt;p&gt;GPG, or GNU Privacy Guard, is a free-software replacement for Symantec&amp;rsquo;s PGP cryptographic software suite.
GPG is not a new cryptographic algorithm. GPG keys are simply those generated by the GPG software using existing
algorithms such as RSA.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;gpg&lt;/code&gt; is a CLI tool for managing keys, and the keys it generates have more features. For example, GPG keys can
expire or be revoked. With GitHub, SSH keys are used for authentication, while GPG keys are used for
signing commits and tags. Commit-signing makes sure the committer is indeed who he/she claims to be &amp;mdash;
otherwise any one can claim to be any one by setting username and password with &lt;code&gt;git config&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>