Play with it, please! Or you could always contribute. Your commits themselves are untouched from git's perspective, so if you mirror your repository elsewhere, it'll be a regular checkout.ĭon't you know I could just do X instead? Crypto is so easy bleah bleah bleah Start a 'one shot' temporary device with a paperkey, useful, e.g., for logging onto Keybase in a Docker container keybase oneshot -help keybase help see all available commands With KBFS running, you'll be able to add files to the magic /keybase directory. Intuitively you can think of it as you and your teammates using a cryptographic secure storage layer for your git origin that doesn't really understand git. No, this is happening at a lower level, (1) to allow encryption, and (2) to ensure no unsigned or unencrypted data makes it in. This is not exposed in the GUI but it can work. Similarly, you shouldn't put git repos in Dropbox.Īlso: it's nicer to use the Keybase app to discover and manage your teams' repositories. Which means you and another team member could be fighting each other and make a conflicted HEAD, where there'd be 2 copies side by side. The Keybase filesystem journals changes and syncs them after writes, kind of like Dropbox. Keybase offers no guarantees against sophisticated side-channel attacks by higher-level entities. Your work is only as safe as your endpoints, so we can't help you there. You can have as many repositories as you want, but the total for your personal repositories can't exceed 100GB. Very high, because sometimes you have to make a product that's better on every axis. Keybase recognizes distinct repositories (for example, it has unique id's for every repo), but it doesn't know what you've named your repositories, your branch names, or any contents. Keybase's servers know who's on your team, who's pushing and fetching, and which devices are being used. YES! Keybase has been working on cryptographically-defined teams for many person-years. ~/ >keybase chat send beliebers "praise be crypto"Ĭheers, because we wanted to make this for a while. You don't need to think about it: if you do a git pull, you'll only get the data if it's bit-for-bit exactly what the pusher pushed.Īnd as a final reminder, Keybase comes with encrypted chat, so your team can discuss your commits with ease. Unlike casual PGP signing of commits, which no one in the world ever does, this is fully enforced for yourself or team. Fetches are cryptographically verified or else they'll fail. You can send or receive Lumens (cryptocurrency), in short XLM. AuthenticityĪll data you push is signed by your device's private key, which never leaves your device. You get encrypted one-to-one or group chat with people on keybase You can encrypt or decrypt any TEXT or FILE in keybase for sharing it anyhow you like. This is stuff we've already built, so this project was 99% done when we started. We bring to the table: (1) crypto, (2) team + multi-device key management, (3) a safer concept of identity. We provide a remote helper, powered by the excellent go-git project, which we've begun contributing to. This might sound impressive, but Keybase has not reimplemented git from scratch. Keybase's remote helper performs all the crypto while letting git do its thing. You'll see a clone address like this: git clone keybase://private/chris/docs.git
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |