<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>gpg &amp;mdash; Chiraag&#39;s Musings</title>
    <link>https://blog.chiraag.me/tag:gpg</link>
    <description>Ramblings at the intersection of socialism and engineering</description>
    <pubDate>Tue, 10 Nov 2026 02:28:00 +0000</pubDate>
    <item>
      <title>New bkup release!</title>
      <link>https://blog.chiraag.me/new-bkup-release</link>
      <description>&lt;![CDATA[#bkup #OpenSource #BackupSoftware #GPG&#xA;&#xA;Two quick QOL updates for bkup:&#xA;&#xA;A new flag --full which does a full (non-incremental) backup whether or not there is a .date/.date.gpg file. This sets --rsync-mode=sync as well.&#xA;A new flag --write-decrypted to write the decrypted .salt and .date files in ${XDGDATADIR} (these will never be stored in ${XDGCACHEDIR}, so they are never uploaded to the cloud).&#xA;&#xA;The first is useful for cases where the contents change quite frequently (e.g. ~/.config), since incremental backups will inflate the storage quite quickly. The second is useful if, like me, you repeatedly forget to decrypt the salt and date files for any newly-backed-up directories.&#xA;&#xA;Next up is probably writing some kind of restore script. In all fairness, restoring is pretty easy: decrypt each chunk, cat them together, run it through zstd -d and then tar -xf (that was the reasoning behind using standard formats like tar and gpg after all). Still, having some kind of restore script is probably a good idea.]]&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://blog.chiraag.me/tag:bkup" class="hashtag"><span>#</span><span class="p-category">bkup</span></a> <a href="https://blog.chiraag.me/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a> <a href="https://blog.chiraag.me/tag:BackupSoftware" class="hashtag"><span>#</span><span class="p-category">BackupSoftware</span></a> <a href="https://blog.chiraag.me/tag:GPG" class="hashtag"><span>#</span><span class="p-category">GPG</span></a></p>

<p>Two quick QOL updates for <a href="https://gitlab.com/chiraag-nataraj/bkup">bkup</a>:</p>
<ol><li>A new flag <code>--full</code> which does a full (non-incremental) backup whether or not there is a <code>.date</code>/<code>.date.gpg</code> file. This sets <code>--rsync-mode=sync</code> as well.</li>
<li>A new flag <code>--write-decrypted</code> to write the decrypted <code>.salt</code> and <code>.date</code> files in <code>${XDG_DATA_DIR}</code> (these will never be stored in <code>${XDG_CACHE_DIR}</code>, so they are <em>never</em> uploaded to the cloud).</li></ol>

<p>The first is useful for cases where the contents change quite frequently (e.g. <code>~/.config</code>), since incremental backups will inflate the storage quite quickly. The second is useful if, like me, you repeatedly forget to decrypt the salt and date files for any newly-backed-up directories.</p>

<p>Next up is probably writing some kind of restore script. In all fairness, restoring is pretty easy: decrypt each chunk, <code>cat</code> them together, run it through <code>zstd -d</code> and then <code>tar -xf</code> (that was the reasoning behind using standard formats like <code>tar</code> and <code>gpg</code> after all). Still, having some kind of restore script is probably a good idea.</p>
]]></content:encoded>
      <guid>https://blog.chiraag.me/new-bkup-release</guid>
      <pubDate>Sat, 07 Nov 2026 21:38:09 +0000</pubDate>
    </item>
  </channel>
</rss>