diff --git a/source/_posts/2015-05-09-gnupg-2-dot-1-2-doesnt-work-with-caff.markdown b/source/_posts/2015-05-09-gnupg-2-dot-1-2-doesnt-work-with-caff.markdown
new file mode 100644
index 0000000..0609b22
--- /dev/null
+++ b/source/_posts/2015-05-09-gnupg-2-dot-1-2-doesnt-work-with-caff.markdown
@@ -0,0 +1,29 @@
+---
+layout: post
+title: "GnuPG 2.1.2 doesn't work with caff"
+date: 2015-05-09 01:50:02 +0200
+comments: true
+categories: 
+---
+
+Today I signed a GnuPG key using my air-gapped master private key,
+and then tried to send the signature to the key owner from
+my network-connected workstation using [caff](https://wiki.debian.org/caff).
+This failed miserably, with caff unable to find a valid signature,
+and `gpg --list-secret-keys` missing the (stub) private key.
+
+It turns out that I had inadvertently upgraded GnuPG on this workstation
+to version 2.1.2, which has a [completely revamped secret keys handling](https://www.gnupg.org/faq/whats-new-in-2.1.html#nosecring):
+secret key material is now entirely handled by `gpg-agent`, and
+the `--secret-keyring` command line option for `gpg` (which `caff`
+depends on) is now
+[obsolete](https://lists.gnupg.org/pipermail/gnupg-devel/2014-December/029296.html).
+
+GnuPG 2.1 apparently also chokes on some legacy keys, and the work-around
+is to [reimport the keyring manually](http://jo-ke.name/wp/?p=111).
+
+`caff` has been [fixed](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771857)
+to support GnuPG 2.1. However this depends on GnuPG 2.1.3 or newer,
+which is [not in the ports tree yet](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200057),
+so for the time being I have reverted
+to the "stable" 2.0 release: `portmaster -o security/gnupg20 gnupg`.
diff --git a/source/_posts/2015-07-30-subsonic.markdown b/source/_posts/2015-07-30-subsonic.markdown
new file mode 100644
index 0000000..db843d9
--- /dev/null
+++ b/source/_posts/2015-07-30-subsonic.markdown
@@ -0,0 +1,42 @@
+---
+layout: post
+title: "Subsonic, FreeBSD 10, and UTF-8"
+date: 2015-07-30 15:00:00 +0200
+comments: true
+categories: 
+---
+
+In the context of
+[upgrading to FreeBSD 10]({% post_url 2015-02-18-upgrading-to-freebsd-10-1-release %}),
+I reinstalled the [Subsonic media server](http://www.subsonic.org/) from ports.
+
+Servlet container
+=================
+
+It turns out that using Jetty as the underlying servlet container would not work:
+I would get an obscure Java exception during various operations:
+
+```
+Message	/WEB-INF/jsp/settingsHeader.jsp(12,0) PWC6340: According to the TLD, rtexprvalue is true, and deferred-value is specified for the attribute items of the tag handler org.apache.taglibs.standard.tag.rt.core.ForTokensTag, but the argument for the setter method is not a java.lang.Object
+```
+
+Switching to Tomcat 8 worked.
+
+Changing filesystem charset to UTF-8
+====================================
+
+I had been using ISO-8859-15 filenames for ever. As part of the OS ugprade,
+I decided it was more than time to switch the whole system to UTF-8. (One
+specific issue that prompted this was the fact that GDM now seems to not
+support ISO 8859-15 GECOS user names anymore).
+
+In order to have Subsonic properly handle file and directory names encoded
+in UTF-8, I had to set LANG for it:
+
+```plain /etc/rc.conf.d/tomcat8
+export LANG=fr_FR.UTF-8
+```
+
+*and* to re-create the database from scratch (remove everything from
+`/var/subsonic/db/` *except* `subsonic.script`).
+