7 Commits (71300489af362c3fed4736de6bffab4d758b6a84)

Author	SHA1	Message	Date
Andrew Chow	207abc147c	doc: Add my key to SECURITY.md	2 years ago
laanwj	38a911e107	doc: Remove my key from SECURITY.md ... As I am no longer on the `security@bitcoincore.org` alias, there is no point in asking people to GPG-encrypt to me. Remove it. Tree-SHA512: f15640b741b908b162acf149ab27dae149fc917c15fbabf8dd9aff7bc6afb9e8b2ae956f9a0f8fbe1f05f40a48215becc1efda90a2e9c1105559cdeafb073060	2 years ago
Tim Ruffing	90f1f849e9	doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.md ... This is in line with 4c43b7d41d from PR #22688.	3 years ago
fanquake	e7c0d506d5	doc: update SECURITY.md inline with recent changes to bitcoincore.org ... See https://github.com/bitcoin-core/bitcoincore.org/pull/809 and https://github.com/bitcoin-core/bitcoincore.org/pull/819 and https://bitcoincore.org/en/contact/.	3 years ago
MarcoFalke	fa4bc4ebf9	doc: Remove explicit mention of version from SECURITY.md	5 years ago
Jon Atack	e4e2b28cf1	doc: clarify support in SECURITY.md	6 years ago
Neha Narula	fdd7fa19a9	docs: create security policy ... Github has started supporting SECURITY.md to contain a project's security policy. Right now, the only place to find this project's security contact is on bitcoincore.org. Adding this information to the repository makes it easier to find as SECURITY.md becomes a standard. This is copied almost exactly from https://bitcoincore.org/en/contact/ and based on conversations with Ethan Heilman.	6 years ago