User:AManNamedEdwan/sandbox

Keybase

Crypto for everyone
File:Chris Coyne (chris) Keybase.png A screenshot of a Keybase user page.
Type of site	Encrypted social networking service
Available in	English
Owner	Keybase, Inc
Created by	Chris Coyne, Max Krohn, others
URL	keybase.io
Registration	Required for membership
Users	178,812
Launched	February 14, 2014 (2014-02-14)
Current status	Open alpha
Written in	Go

Keybase is a site which "maps [a user's] identity to [thier] public keys, and vice versa." Currently, Keybase allows a user to prove Twitter, GitHub, Facebook, Reddit, and Hacker News identities, along with Bitcoin and Zcash wallet addresses. Keybase supported Coinbase identities but ceased to do so 17 March 2017 when Coinbase terminated public payment pages. Keybase also offers an encrypted chat and cloud storage system, called the Keybase filesystem. Files placed in the public portion of the filesystem are served from keybase.pub, as well as locally from a filesystem mounted by the Keybase client.

Client

In addition to the web interface, Keybase offers a client application for Windows, OSx, Android, iOS, and most desktop Linux distributions, written in Go with an Electron front end. The client offers additional features to the website, such as the ability to add files to the Keybase filesystem and access private files in the system. Each device running the client is authorized by a signature made either by another device or the user's PGP key. Each device is also given a per-device NaCl key to perform cryptographic operations.

Keybase Filesystem (KBFS)

Keybase allows users to store up to 10 GB of files in a cloud storage called the Keybase filesystem. The filesystem is divided into three parts: public files, private files, and team files. On Unix-like machines, the filesystem is mounted to /keybase, and on Microsoft Windows systems it is usually mounted to the K drive. Currently, mobile versions of the Keybase client do not have any user interface for interacting with the filesystem. However, they do support operations such as rekeying files as necessary.

Public Files

Public files are stored in /public/username, and are publicly visible. All files in the public filesystem are automatically signed by the client. Only the user who the folder is named after can edit its contents, however, a folder may be named after a list of comma-separated users (e.g. a folder /public/foo,bar,three would be editable by the users foo, bar, and three.)

Public files can be accessed by any user. Single user folders are displayed at keybase.pub and are also accessible by opening the directory in the mounted version of the filesystem. Multi user folders (such as /public/foo,bar,three) are only accessible through the mounted version of the system.

Private Files

Private files are stored in /private/username, and are only visible to username. Private files, like public files, can be named after more than one user (e.g. a folder /public/foo,bar,three would be readable and editable by the users foo, bar, and three.) Unlike public files, all private files are both encrypted and signed before being uploaded, making them end-to-end encrypted.

Teams

On 2017-09-18, Keybase launched a "teams" feature. Teams are described as "...a named group of people." Each team has a private folder in the Keybase filesystem, and a number of chat channels (similar to Slack.) Teams can also be divided into "subteams" by placing a . in the team name. For example, wikipedia.projects would be a subteam of wikipedia, while wikipedia.projects.foobar would be a subteam of wikipedia.projects (and therefore, also of wikipedia.)

Team Administration

Teams are largely administrated by adding signatures to a chain. Each signature can add, remove, or change the membership of a a user in a team, as well as when changes are made to subteams.

Each chain starts with a signature made by the team owner, with subsequent actions signed on by team admins.