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: GroupWise
date: 2019-08-08T02:59:36.000Z
replaces: []
weight: 30
lastmod: 2019-08-22T02:35:41.000Z
---
### What is GroupWise?
GroupWise is a messaging and collaboration platform originally developed by
WordPerfect Corporation and later acquired by Novell but now owned by [Micro
Focus](https://www.microfocus.com/en-us/products/groupwise/overview). (See [this
Wikipedia article](https://en.wikipedia.org/wiki/GroupWise) for details.) The
Groupwise protocol within Pidgin specifically supports the instant messaging
portion of the GroupWise platform. Much of Pidgin's support for the GroupWise
Messenger service was generously provided by Novell several years ago.
### Are there any public servers?
No. This protocol is designed to connect with a GroupWise Messenger server
running on a corporate LAN. There are no known public servers.
### I can't get it to work.
We are told this protocol plugin works only with the GroupWise Messenger for
Linux server or the GroupWise Messenger SP2 (or later) server running on NetWare
or Windows, and then only if the server is secure (SSL/TLS-enabled).