<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tip on Quentin's blog</title><link>https://blog.qligier.ch/tags/tip/</link><description>Recent content in Tip on Quentin's blog</description><generator>Hugo</generator><language>en-us</language><copyright>© 2025 Quentin Ligier</copyright><lastBuildDate>Wed, 28 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.qligier.ch/tags/tip/index.xml" rel="self" type="application/rss+xml"/><item><title>Verifying SSH and GPG keys for Forgejo/Gitea with PowerShell 7</title><link>https://blog.qligier.ch/posts/2026-verify-ssh-gpg-keys-forgejo-gitea-powershell7/</link><pubDate>Wed, 28 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog.qligier.ch/posts/2026-verify-ssh-gpg-keys-forgejo-gitea-powershell7/</guid><description>&lt;p&gt;I recently created a user account on a Forgejo/Gitea instance, as I wanted to contribute to a project hosted on that
platform.
To keep a coherent Git setup across the different development platforms, I wanted to add my SSH and GPG keys, and
discovered that Forgejo/Gitea requires a verification step to ensure the ownership of the keys.
This verification step involves signing a specific single-use token with the respective key and then submitting the
generated signature back to Forgejo/Gitea.&lt;/p&gt;</description></item></channel></rss>