Security issues

Open
#11 0 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation, security

Research direction

Start by reviewing the platform whitepaper and the three security questions in this issue. Done would require an agreed scope and documented answers covering preventive measures, expected security features, vulnerable attack types, and planned countermeasures.

Written by the indexing model from the issue text.

Description

I was pretty surprised to see there was a whitepaper with no mention of security

  1. How is the platform plan to be developed to take preventive measures against attacks?
  2. What security features are expected?
  3. What types of attacks might the platform be vulnerable to and what counter measures are planned to lower the risk of those attacks?
Dominant language
No language data
Stars
2k
Forks
860
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EOSIO/Documentation

All issues in EOSIO/Documentation

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.