Looking for Parity Ethereum client? Get it here.

New GPG key for security@parity.io

Image Kirill Pimenov
Head of security @ Parity Technologies
July 17, 2019 in Security

At Parity we’re always looking for ways to improve our security. As phishing exploits continue increasing in sophistication, we have been thinking about how to ensure the trustability of our critical security messages.

We receive critical security messages through security@parity.io. In order to ensure that the recipient can trust that we are the only receiver of these emails, they encrypt their message with GPG keys, which enable signing and encrypting emails.

GPG keys have a two-year lifespan and it’s possible to extend the lifetime of the keys. However, when facing the end of our security@parity.io key lifespan, out of an abundance of caution we decided to issue a new key instead of extending the existing key.

Up until Sunday July 21, 2019, our security@parity.io GPG key has this fingerprint:
DAE5 1560 28CF 37A0 7C69  3883 5D0F 0301 8D07 DE73

Starting on Sunday July 21, 2019, our security@parity.io GPG key has this fingerprint:
9D4B 2B6E B8F9 7156 D196  69A9 FF08 12D4 91B9 6798

The keys are available on SKS pool, as well as on keys.mailvelope.com and keys.openpgp.org independent keyservers. We suggest you try independent keyservers if you are not able to retrieve our keys from SKS because of certifications DoS attacks.

To learn more about GPG keys and how to set them up on your emails, check out this guide.

If you have any questions or want to discuss GPG keys, join the conversation at the Parity Watercooler chat.

Please find a signed version of this announcement in the following gist: https://gist.github.com/kirushik/61d317955652c4933514e5c73cb7c6be

Want to build the future of the web? We're hiring

More recent stories

September 16, 2019

Preparing for Istanbul: New Parity Ethereum release

Read More
September 02, 2019

People of Parity: Shawn Tabrizi

Read More
August 29, 2019

New Parity Ethereum update protects against RPC call vulnerability

Read More

Join the discussion:

--}}