pidgin/nest

Add pgp public key and refer to it in our security disclosure method

The idea behind this is to make sure people that choose to use email to let us
known about a potential security issue in Pidgin encrypt the content of the
emails using a set of pgp keys of trusted Pidgin developers. For now we only
have the pgp key of grim but more keys can easily be added later on.

At the same time, since Hugo does not currently have a built-in shortcode for
linking directly to static resources, I had to add a new shortcode for doing so

Testing Done:
Ran `dev-server.sh` and made sure content looked as intended and links worked.

Bugs closed: NEST-46

Reviewed at https://reviews.imfreedom.org/r/860/
---
title: "2.14.1 Released!"
date: 2020-06-11T04:48:05-05:00
replaces: []
---
**Updated 2021-02-04 to strike out Bintray mentions as they have
[announced](https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/)
that they are sunsetting it. See
[Bintray Sunsetting]({{< ref "bintray-sunsetting.md" >}})**
So who would have guessed that some stuff would go wrong when we haven't
released in nearly two years?
The changes for 2.14.1 are small but important. There were some issues with
the Windows installer that made it impossible to install 2.14.0 and the
Mercurial revision in the About box was displaying "unknown".
Sorry for the inconvenience that this may have caused!
You can find 2.14.1 on
[SourceForge](https://sourceforge.net/projects/pidgin/files/Pidgin/2.14.1/)
~~as well as on
[Bintray](https://bintray.com/pidgin/releases/pidgin/2.14.1)~~.