Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add post on security vulnerability #361

Merged
merged 6 commits into from Apr 8, 2020
Merged

Add post on security vulnerability #361

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ad31ea3
Add post on security vulnerability
Apr 8, 2020
8ccec2c
Move date from title to permalink
Apr 8, 2020
557aae2
Change wording on payouts
Apr 8, 2020
d3aeb70
Change wording on years in operation
Apr 8, 2020
81bef29
Revise ending
Apr 8, 2020
c3587a0
Add link to 1.3 release
Apr 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2020-04-08-statement-security-vulnerability.md
View file
Open in desktop
Expand Up @@ -19,4 +19,4 @@ A proposal will soon be created in the Bisq DAO, Bisq’s funding mechanism, tha

Security has always been a top priority for Bisq, but this incident shows it wasn't perfect. The project is evaluating several approaches to strengthening security reviews and practices even more, and will detail them soon.

The Bisq developer community sincerely apologizes. In the past 6 years, Bisq has never had to use the alert key to enable “safe mode” on Bisq nodes, and this is an unprecedented case for the Bisq DAO.
The Bisq developer community sincerely apologizes. In the past 4 years of operating on mainnet, Bisq has never had to use the alert key to enable “safe mode” on Bisq nodes, and this is an unprecedented case for the Bisq DAO.