Pulshade has not yet had an independent audit. The ratchet, the handshake and the envelopes are our own code following published designs, and the apps are open source so anyone can check them. If you want to understand the design first, read how Pulshade works.
How to report
Please don’t open a public issue.
Report it privately through GitHub: on Pulshade’s public source repository, open the Security tab and choose Report a vulnerability. Only the maintainer sees it.
You’ll get a reply as soon as possible, and we’ll agree on when to make it public once a fix is out. If you’d like, you’ll be credited in the release notes.
What to include
- What an attacker can do, and what they need first (a network position, the relay, a stolen device, a contact).
- The steps to reproduce it, or a proof of concept.
- The version or commit you tested.
What counts
Anything that breaks a promise Pulshade makes, for example:
- reading messages, calls, files or stored data without the keys
- forging or replaying messages, or impersonating someone
- linking identities, personas or devices to each other, or revealing someone’s IP address while Tor is on
- telling whether a decoy or panic passcode is set up
- the relay learning more than it should, accepting admin actions it shouldn’t, or losing other people’s messages
- recovering anything after Lock, Detach or Burn that should be gone
Testing safely
Use your own accounts. Please don’t load-test or attack Pulshade’s servers. Don’t access anyone else’s data, and stop as soon as you’ve shown the problem.
Research done in good faith along these lines is welcome, and won’t be treated as an attack.