Keybase proof gist how to#
Keybase proof gist serial#
Keybase proof gist driver#
Keybase proof gist verification#
Keybase proof gist code#

Keybase proof gist code#

Here’s an example of some code that might work to create a new proof. # on the given `domain` or a subdomain and accessible via HTTPS. # See the Protocol section for an explanation of these urls. 'description': 'Next gen social network using big data & AI in the cloud 🤖☁️.', # Assets will be rehosted by Keybase, so do let us know about updates. # Your brand logo will appear in various places around the Keybase app. # Keybase will treat these case-insensitively and will only display usernames # (inline flags, like for case-insensitivity, are not supported). # A regex for validating usernames on Bee Activists in the re2 format # Please version bump when updating config All of the fields are required unless noted as optional, and all Let’s start with the config file, which has all the information Keybase needs Throughout this document our examples are written using httpie for simplicity. We also have a Clojure reference implementation using a Clojure helper library.

Keybase proof gist verification#

To help with your integration we have a Python reference implementation if you prefer to consume the material that way and a verification script for testing things out. You’ll also send us a config file (described below) which we’ll use to finish out the integration. Integrating with Keybase as an identity service involves implementing some product features, a couple API endpoints, and then talking to us. In this guide, let’s call your service the Identity Service, though we both know it’s so much more. Linking you and Keybase will link to each other, but only upon a successful proof.Proof checking the proof signature can be requested from your service, and cryptographically checked by anyone.Proof creation this is when the user signs a statement in Keybase, claiming to be a member of your service.Getting startedĪs you read this guide, you’ll go through: If you are looking to prove your identity on a personal instance then an https proof of the domain should do the trick, proving that you own that instance. Many instances are in listed in the Keybase app but we have paused adding new instances for now. Mastodon has built-in support for Keybase proofs starting with version 2.8.0. This short guide is a walkthrough of the endpoints you’ll need to implement to make it happen.

Keybase proof gist how to#

Also, Keybase profiles will appear on the profiles of your service, allowing users to know how to reach each other securely. In other words, your service can join Reddit, Twitter, Github, and Facebook on Keybase profiles. And, going in the other direction, you can start with something she signed, and know for certain it was signed by Twitter user we are opening up a set of steps that your app or website can follow to get cryptographic connections to Keybase. travis.yml CHANGELOG.md CONTRIBUTORS.md LICENSE Makefile README.md SIGNED.md package-lock.json package.json teamssample.cson testscraper.iced yarn.lock README. If you know on Twitter, Keybase can provide you her keys and proof that they are in fact her keys. GitHub - keybase/proofs: Public Keybase Proof System master 33 branches 205 tags Code 850 commits Failed to load latest commit information. (Thanks to tammy for letting us use her happy profile as an example in the app store.) For example, it isĬryptographically proven that Keybase user tammy is all of these identities: You still need a dumb LIN level shifter chip to actually communicate on the LIN buss, but that is much cheaper than a dedicated CAN transceiver chip with it's own logic.The most basic idea behind Keybase is that it’s a protocol and directory for connecting people’s identities and keys together.

Keybase proof gist serial#

The Microchip DSPIC33CK family (the family I am most familiar with) has several instances of a USART peripheral with specific modes for LIN and several other serial protocols, because the LIN wire format is extremely similar to UART. Another reason UART is so common is that protocols like LIN can be implemented in the same hardware.

Keybase proof gist driver#

LIN takes quite a bit of setup, writing the LDF, configuring the LIN driver on the micro, then writing or using expensive and inflexible software to communicate on a protocol that is kind of alien to the way most protocols on PCs are layered. Also for on board micro to micro communications UART is a fine choice to build a simple protocol on top of. And if I'm in a hurry I can just use printf and get easy readout of what's going on in the micro. Then: gpg -allow-secret-key-import -import keybase-private.key Git Once you’re all set with your Keybase stuff, you need to teach your git how to crypto. During development I can get a simple uart channel configured in 5 minutes and hook it up to my computer for diagnostics extremely quickly. Open your Keybase profile, and Confirm password, copy everything from the popup and save it as ex. First off, protocols like CAN and LIN are extremely complicated and inflexible compared to uart. As someone who works in automotive embedded development I have some comments on this.