keybase / keybase/keybase-issues

Possible Typo in keybase.io/docs/server_security/tracking docs

Open
#2,188 2 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

Step 2: the computer review

> In simplest terms, the Keybase client guarantees that "maria" has access to three things: (1)
> the Keybase account, (2) the twitter account, and (3) the **private key** referenced back in step 1.

(**emphasis mine**)

This should be **public key**, right?

The JSON object in step 1 says the following `keybase_username` has this `public_key`, `twitter_username`, and `twitter_proof`. I get that "maria" should have the private key corresponding to that public key, but isn't that too strong a statement?

Contributor guide

No contributing guide indexed for this repository

Research direction

Open keybase.io/docs/server_security/tracking and compare the Step 2 wording with the JSON object described in Step 1. Confirm whether “private key” should be “public key,” then update the sentence so it accurately reflects the information established by the proof; the issue is done when the documentation no longer makes the stronger claim.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.