Doichain/dapp

revoke permission specification and compromised privateKeys approach

Open

#58 opened on Aug 31, 2018

View on GitHub
 (1 comment) (0 reactions) (1 assignee)JavaScript (13 forks)auto 404
bountyenhancementfeaturehelp wantedsecuritytest

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

when a DOI (permission) was given, so far it stays with the ownership of Bob (email provider), which is correct and should NOT be changed.

in case Peter (the recipient) wants to revoke a permission he should browse his permission on his responsible Doichain dApp (Bob) and revoke the permission for a sender (Alice) there.

As soon as Bob revokes he should identically inform Alice about the revocation as he did for the confirmation. Alice now deletes (or better flag revoked = true) her local records of Peter automatically.

Please see https://bounties.doichain.org/ how to apply for Doichain bounties.

Contributor guide

Research direction
Investigate the current permission handling in the Doichain dApp, focusing on how permissions are granted and stored. Study the revocation flow described in the issue and trace the code related to permission management. Look for existing functions that handle permission confirmation and adapt them for revocation. Ensure that when Bob revokes a permission, Alice's local records are updated with a revoked flag.
Tech stack
javascriptnodejs
Domain
full stack
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitJavaScriptMeteor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50