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

Assessment: creation of blocklist and allowlist of data request sources to prevent inconsistent source attacks #1096

Open
lrubiorod opened this issue Mar 18, 2020 · 0 comments
Open

Assessment: creation of blocklist and allowlist of data request sources to prevent inconsistent source attacks #1096

lrubiorod opened this issue Mar 18, 2020 · 0 comments
Labels
assessment 🧐 Needs preliminary evaluation/study/assessment work security 🛡️ Changes that affect software security for the good or the bad

Comments

@lrubiorod
Copy link
Contributor

Currently is very easy to create a Data Requests which penalise honest witnesses (Inconsistent source attack).

The idea is to create two lists (allowlist and blocklist), that provide information about data requests sources that are safu or not. By example, safuness could be tested acceding to the source through TOR and without TOR and checking that the same response is obtained.
@lrubiorod lrubiorod added the assessment 🧐 Needs preliminary evaluation/study/assessment work label Mar 18, 2020
@aesedepece aesedepece changed the title Assesment: creation of blocklist and allowlist of data request sources to prevent inconsistence source attacks Assessment: creation of blocklist and allowlist of data request sources to prevent inconsistent source attacks Mar 18, 2020
@lrubiorod lrubiorod mentioned this issue Mar 18, 2020
Closed
@aesedepece aesedepece added the security 🛡️ Changes that affect software security for the good or the bad label Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
assessment 🧐 Needs preliminary evaluation/study/assessment work security 🛡️ Changes that affect software security for the good or the bad
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aesedepece @lrubiorod