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

Review Request #860 — Created Aug. 3, 2021 and submitted

Information

pidgin/nest
default
a67a7f977ebc

Reviewers

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

Ran dev-server.sh and made sure content looked as intended and links worked.

Description From Last Updated

Creating an issue in my own RR to emphasize on the need for grim to double check that the pgp …

sorvivalsorvival

I'd reword this to say something like If you choose this method and would like to encrypt the contents... I …

grimgrim
sorvival
  1. 
      
  2. Show all issues

    Creating an issue in my own RR to emphasize on the need for grim to double check that the pgp key I'm including here is indeed the one you posted in Youtrack.

    1. I compared to gpg --export -a 40DE1DC7288FE3F50AB938C548F66AFFD9BDB729 and it does look correct.

  3. 
      
grim
  1. 
      
  2. hugo/content/about/security/_index.md (Diff revision 1)
     
     
    Show all issues

    I'd reword this to say something like If you choose this method and would like to encrypt the contents... I don't think we need to force people to setup gpg if they don't already have it setup.

  3. 
      
sorvival
grim
  1. Ship It!
  2. Awesome work, thanks!!

  3. 
      
grim
Review request changed
Status:
Completed