keybase / keybase/keybase-issues

Tracking & web of trust

Open
#887 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I know there have been a few other issues on what exactly "tracking" means - e.g. #100 (I don't understand tracking) and #499 (what is the meaning of 'tracking'?). I want to know, is there a method to not simply track someone's key as a way of adding it to your keyring & knowing when it has been changed / additionally proven, but also to add a relationship within the web of trust? Some related questions:
1. When I track someone, do I sign their key (i.e. say that I trust them in the web of trust) as part of this process automatically?
2. If, for example, I know and trust @malgorithms and know that their public key really belongs to them, is there a method via keybase in which I could add the web of trust information to keybase.io/chris?

I would suggest, if this is not already a part of the tracking system (and I may be misunderstanding it) that when you "track" someone, an interactive prompt question should appear asking if you trust them as well, and which level of trust (no checking, casual checking, very careful checking of the person's identity).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the tracking behavior discussed in related issues #100 and #499, then determine how tracking currently relates to key changes and additional proofs. Done would clearly specify whether tracking signs a key, how an existing trusted relationship can be added, and how trust levels should be selected.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.