From ArchWiki
Revision as of 02:56, 6 January 2018 by ToxygeneB (talk | contribs) (Initial draft)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: This article is a draft. (Discuss in Talk:Keybase#)

From Wikipedia:

Keybase is a key directory that maps social media identities to encryption keys (including, but not limited to PGP keys) in a publicly auditable manner. Keybase also offers an encrypted chat and cloud storage system, called Keybase Chat and the Keybase filesystem respectively. Files placed in the public portion of the filesystem are served from a public endpoint, as well as locally from a filesystem mounted by the Keybase client. Keybase supports publicly connecting Twitter, GitHub, Facebook, Reddit, and Hacker News identities to encryption keys, along with Bitcoin and Zcash wallet addresses.


Keybase is provided by the keybase package, however this does not yet include the GUI or the KBFS filesystem. If you want the GUI and KBFS filesystem install keybase-binAUR.

After installing or updating, run:

$ run_keybase

Signup / Login

To signup for a Keybase account use, and follow the on-screen prompts:

$ keybase signup

If you already have a Keybase account you can login with:

$ keybase login <keybase_username>

GnuPG Keys

During the interactive signup if you already have any GnuPG key pairs on your keyring, Keybase will ask if you wish to use one of them. If you do not have a key pair, you can generate one with:

$ keybase gpg gen

This will interactively generate a key pair and securely upload the keys.

Keybase Filesystem (KBFS)

KBFS uses FUSE to mount the remote cryptographic filesystem via the systemd unit keybase.mount.

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. The filesystem is mounted to /keybase.

All files under /keybase/public are automatically signed by the client. All files under /keybase/private files are both encrypted and signed before being uploaded, making them end-to-end encrypted.

See also