<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gnupg on vxlabs</title>
		<link>https://vxlabs.com/tags/gnupg/</link>
		<description>Recent content in Gnupg on vxlabs</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 24 Oct 2024 08:01:57 +0200</lastBuildDate>
		
			<atom:link href="https://vxlabs.com/tags/gnupg/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>OpenPGP WKD for easy PGP key discovery</title>
				<link>https://vxlabs.com/2024/10/24/openpgp-wkd-for-easy-pgp-key-discovery/</link>
				<pubDate>Thu, 24 Oct 2024 08:01:57 +0200</pubDate>
				<guid>https://vxlabs.com/2024/10/24/openpgp-wkd-for-easy-pgp-key-discovery/</guid>
				<description>&lt;p&gt;Web Key Directory (WKD) &amp;ldquo;is a standard for discovery of OpenPGP keys by email address, via the domain of its email provider&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;In short, through some DNS and files-on-your-webserver conventions, some email clients (e.g. Thunderbird or ProtonMail) and tools like GnuPG are able to retrieve your PGP keys automatically. This is of course super convenient and desirable for your correspondents, because PGP encryption is hard enough as it is.&lt;/p&gt;&#xA;&lt;p&gt;OpenPGP makes this even better by offering &amp;ldquo;WKD as a service&amp;rdquo;, which means you only have to do the DNS bits, and not the files-on-your-webserver bits.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Configure Thunderbird 128 e2e encryption with GnuPG</title>
				<link>https://vxlabs.com/2024/08/09/configure-thunderbird-128-e2e-encryption-with-gnupg/</link>
				<pubDate>Fri, 09 Aug 2024 13:55:52 +0200</pubDate>
				<guid>https://vxlabs.com/2024/08/09/configure-thunderbird-128-e2e-encryption-with-gnupg/</guid>
				<description>&lt;p&gt;It took me longer than I would have liked to setup the latest Thunderbird 128 (Supernova!) to use my &lt;a href=&#34;https://cpbotha.net/2016/12/11/pgp-never-gonna-give-you-up/&#34;&gt;existing&#xA;GnuPG-based encryption setup&lt;/a&gt;, for a large part because TB&#xA;defaults to its own more straight-forward built-in defaults for key management, and so I&amp;rsquo;m going to publish the recipe&#xA;here to save you some time, hopefully.&lt;/p&gt;&#xA;&lt;p&gt;All the details, at various levels of obviousness, can be found on &lt;a href=&#34;https://wiki.mozilla.org/Thunderbird:OpenPGP:Smartcards#Allow_the_use_of_external_GnuPG&#34;&gt;this Mozilla wiki page&lt;/a&gt;, but here I&amp;rsquo;m going to make the whole sequence more obvious.&lt;/p&gt;</description>
			</item>
			<item>
				<title>GnuPG pinentry via the Emacs minibuffer</title>
				<link>https://vxlabs.com/2021/03/21/gnupg-pinentry-via-the-emacs-minibuffer/</link>
				<pubDate>Sun, 21 Mar 2021 10:12:00 +0200</pubDate>
				<guid>https://vxlabs.com/2021/03/21/gnupg-pinentry-via-the-emacs-minibuffer/</guid>
				<description>&lt;p&gt;On the various and different platforms where I use Emacs and GnuPG encryption,&#xA;I&amp;rsquo;ve traditionally always had a bit of a struggle setting up a suitable&#xA;mechanism for private key passphrase entry, or pinentry.&lt;/p&gt;&#xA;&lt;p&gt;Recently, I landed upon this extremely easy-to-setup and reliable solution&#xA;where Emacs and GnuPG can be configured so that Emacs requests the passphrase&#xA;via its standard minibuffer password entry mechanism, and then passes this&#xA;through to GnuPG.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
