Skip to content

Latest commit

 

History

History
67 lines (51 loc) · 2.82 KB

DISCLOSURE_POLICY.md

File metadata and controls

67 lines (51 loc) · 2.82 KB
Raw

Responsible Disclosure Policy

DeVault takes security very seriously. We greatly appreciate any and all disclosures of bugs and vulnerabilities that are done in a responsible manner. We will engage responsible disclosures according to this policy and put forth our best effort to fix disclosed vulnerabilities as well as reaching out to numerous node operators to deploy fixes in a timely manner.

Responsible Disclosure Guidelines

Do not disclose any bug or vulnerability on public forums, message boards, mailing lists, etc. prior to responsibly disclosing to DeVault and giving sufficient time for the issue to be fixed and deployed. Do not execute on or exploit any vulnerability. This includes testnet, as both mainnet and testnet exploits are effectively public disclosure. Regtest mode may be used to test bugs locally.

Reporting a Bug or Vulnerability

When reporting a bug or vulnerability, please provide the following to security@bitcoinabc.org:

  • A short summary of the potential impact of the issue (if known).
  • Details explaining how to reproduce the issue or how an exploit may be formed.
  • Your name (optional). If provided, we will provide credit for disclosure. Otherwise, you will be treated anonymously and your privacy will be respected.
  • Your email or other means of contacting you.
  • A PGP key/fingerprint for us to provide encrypted responses to your disclosure. If this is not provided, we cannot guarantee that you will receive a response prior to a fix being made and deployed.

Encrypting the Disclosure

We highly encourage all disclosures to be encrypted to prevent interception and exploitation by third-parties prior to a fix being developed and deployed. Please encrypt using this PGP public key with id: E624CA68344A4AB5DE16183C54094D41BC4E0E77 or '6D6A71D105D30655A1544B098E1A1929A5B461FC'

It may be obtained via:

gpg --recv-keys 6D6A71D105D30655A1544B098E1A1929A5B461FC

Below are some basic instructions for encrypting your disclosure on Linux if you are unfamiliar with GPG:

  1. If you don’t already have a PGP key, first download GPG: For Debian based distributions:
sudo apt-get install gpg

For Archlinux based distributions:

pacman -S gnupg
  1. Generate a PGP key:
gpg --full-generate-key
  1. Select “RSA and RSA”
  2. Enter a key size of 4096.
  3. Follow the remaining prompts.
  4. Save your disclosure report to a plain text file, then encrypt:
gpg --output mydisclosurefile.asc --encrypt --recipient security@devault.cc mydisclosurefile

Backup PGP Keys

These PGP fingerprints and emails are provided only as backups in case you are unable to contact DeVault via the security email above.

jon spock

jonspock at protonmail dot com
6D6A71D105D30655A1544B098E1A1929A5B461FC

proteus

pro at proteanx dot com
E624CA68344A4AB5DE16183C54094D41BC4E0E77