To a viewer, and let them encrypt or verify. keybase-unofficial-core provides core utility methods, keybase-unofficial-api provides an. This works even if they have yet to join Keybase. This library is a wrapper over three individual libraries. It's an easier chat, and it's end-to-end encrypted. Three, you can search Keybase from any page on the web, present results Keybase for Chrome is an official Keybase extension for composing ENCRYPTED messages to any Twitter, Facebook, Reddit, HackerNews, or Github user, from the convenience of your browser. Acceptable values are:Īlso note that this API call, along with both user/autocompleteĪnd username/pgp_keys.asc is available via AJAX using CORS. To avoid getting more data than you need, you can (should!) specify a comma-separated list of fields you desire. (See the user objects page in the documentation for more info.) keybase paperkey make a new paper key keybase device list see your paper keys. You should have at least 1, until Keybase releases a mobile app. You can have as many paper keys as you like. It's a full-powered key, just like a device key. The above example is a pretty small result.Ī user object is a large dictionary and could contain pretty muchĮverything about a user that you have access to. When you install Keybase for the first time, you'll be asked to generate a paper key. It will only return legitimate matches, and therefore its length could be 0, 1, or more. than trying to work with the Keybase API (although it is still in beta). Unlike a usernames lookup, this resulting array cannot have any null values in it. It feels like all I do is write code that calls to an API, whether it be in. Why? Well, multiple people may prove ownership of a domain, and possibly other search fields. We imagine this is easier to deal with.įor external identities, such as domains, this API only supports passing one lookup item at a time (no comma-separated list), but the returning result is still an array. If you pass a comma-separated usernames parameter with N names, you will get back a matching N-sized array, but with null for any users who could not be found. " csrf_token": "lgHZIDQ1NTU0ODE3NzY5ZmM5N."} " bundle": "-BEGIN PGP PUBLIC KEY./*cropped for display*/", such as `domain` and `usernames` (which itself can be a list) I'm still looking into who I need to contact about getting Keybase.io and on the "nice list", as currently our proxy blackholes it with a bunker buster certificate that pretty much can't be trusted.// note that `them` is an array because certain lookups Once that is done, double click the certificate to view it, then expand the Trust arrow and give it System-wide Always Trust and you should be able to talk using golang tools like hub without getting this error. Open Keychain Access and navigate to the certificate in question under System and then drag and drop it onto login to initiate the copy, at which point you need to provide sudo capable credentials. Another workaround is to copy the certificate to the login keychain associated with your user and give it full trust there. There was a bug a for a while in Go (not sure if it is fixed, golang/go#24652) where it has issues accessing the certificates from System or SystemRoot, one workaround is to toggle the trust to Never Trusted and then back to Always Trusted, this triggers an update of the cert in the keychain which sometimes allows Go to correctly find/use them. Do you have the SSL certificates used by the proxies in the System.keychain as "Always Trusted"?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |