aboutsummaryrefslogtreecommitdiff
path: root/SECURITY.md
AgeCommit message (Collapse)Author
2022-08-23doc: Add my key to SECURITY.mdAndrew Chow
2022-08-15doc: Remove my key from SECURITY.mdlaanwj
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
2021-11-08doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.mdTim Ruffing
This is in line with 4c43b7d41d11072f382f938379d21cd2e0bcbb47 from PR #22688.
2021-11-06doc: update SECURITY.md inline with recent changes to bitcoincore.orgfanquake
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/.
2019-06-14doc: Remove explicit mention of version from SECURITY.mdMarcoFalke
2019-06-07doc: clarify support in SECURITY.mdJon Atack
2019-06-05docs: create security policyNeha Narula
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.
generated by cgit v1.2.3 (git 2.26.2) at 2024-11-04 17:54:19 +0000