keybase / keybase/client

App design questions :-)

Open
#9,109 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Hello, keybase is e2e, which means the server (api.keybase.io) should not know anything about msgs between peers; all messages go through the server, so i have a couple of questions:

  • What is the passphrase used for?

  • Is connection between the client-server using a stream cipher or a block cipher? (which one?)

  • Are you using Diffie-Hellman to exchange new keys for encryption in each session against the client-server?

  • How is e2e ensured in the app?

thanks for your time, i'm using keybase :-) great work!

Fernando

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.

Research direction

No files, tests, or entry points are mentioned. The issue needs authoritative answers about passphrase use, client-server cipher and key exchange, and how end-to-end encryption is ensured before a concrete change or completion test can be defined.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.