<?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 joh.fi</title><link>https://joh.fi/categories/gnupg/</link><description>Recent content in Gnupg on joh.fi</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 02 Jan 2015 11:18:14 +0000</lastBuildDate><atom:link href="https://joh.fi/categories/gnupg/index.xml" rel="self" type="application/rss+xml"/><item><title>How to fix your damaged gnupg database</title><link>https://joh.fi/blog/2015-01-02-howto-fix-your-damaged-gnupg-databse/</link><pubDate>Fri, 02 Jan 2015 11:18:14 +0000</pubDate><guid>https://joh.fi/blog/2015-01-02-howto-fix-your-damaged-gnupg-databse/</guid><description>&lt;p&gt;Some time ago I had troubles with my gnupg installation. Namely gpg was unable
to read keys from my trustdb.gpg. I figured this had something to do with the
upgrade to GnuPG 2.1.0.&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-sh"&gt;cd ~/.gnupg
mv pubring.gpg pubring-$USER.gpg
mv secring.gpg secring-$USER.gpg
mv trustdb.gpg trustdb-$USER.gpg
gpg --import pubring-$USER.gpg
gpg --import secring-$USER.gpg
rm pubring-$USER.gpg secring-$USER.gpg
rm trustdb.gpg
mv trustdb-$USER.gpg trustdb.gpg
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That&amp;rsquo;s all for now folks and happy new year!&lt;/p&gt;</description></item></channel></rss>