Hi, I have recently switched web servers and had forgotten to move the keybase.txt file along, so rightfully I got the message that the web proof couldn't be verified. I have put the file back in place and checked it's working but can't re-enable the proof.
The keybase.io web server says it's not there (although it is) and the keybase app says it can't generate a new one because it's already present.
Any suggestion?

• https://keybase.io/fhorlaville
• https://www.tamsoftware.info/keybase.txt

Thanks

In Spotify one could create a public playlist named "Keybase" and add the proof (300 chars max) in the description field, which could then be verified directly from the web..
(moved from keybase/client#5974)

Refactor the Scraper class hierarchy and add a new HTTPs/Web proof for keybase/keybase-issues#28

My username on HN is RoxasShadow (karma 16), but keybase (browser) can't prove it (I asked my HN account to be proved yesterday, so the cache should not be an issue.).
If I reload my profile page, I notice that the username is shown lower-cased even though I wrote it correctly:

Is this the reason, maybe?

Posted in keybase/client#7880 but likely belongs here instead as it would be a new scraper.

It would be "useful" in the I've been kicking around "these parts" of the internet to be able to verify against SLASHDOT-current:

eg: a blog post at: https://slashdot.org/~OctaneZ

https://slashdot.org/journal/2912197

Could be a simple blob with signature added to any page, given that a specific revision can be fetched, and that the user name is posted on that fetched revision. Any one of the sites can be used, but a separate fetch should be done to verify that the user has a unified entry. Otherwise the user is only valid on the given site. The value for "CentralAuth" gives the central identifier, the value for "local" gives the identifier for the local site. That is the "local" is the id for site the request hits, and "CentralAuth" is the id in common for all the unified accounts.

I am not sure how it si possible to verify if a specific wiki is within a wiki set. It is probably best to just use this as a prof for a specific wiki, and possibly for an unified account as such. Possibly call it a "Wikimedia Unified Account" or something similar.

There are other ways to do this, but this can be done in a non-cooperative fashion.

Example blob on a ordinary page https://no.wikipedia.org/w/api.php?action=query&prop=revisions&titles=Bruker:Jeblad/blob&rvprop=user|content
Example struct on a specific user https://no.wikipedia.org/w/api.php?action=query&list=users&ususers=Jeblad&usprop=centralids
API doc https://no.wikipedia.org/w/api.php
About unified login https://meta.wikimedia.org/wiki/Help:Unified_login
About CentralAuth https://www.mediawiki.org/wiki/Extension:CentralAuth

I have Google Sites set up on one of my domains and tried to create a proof for my identity. The proof is at http://mbirth.de/keybase.txt . However, Google makes a real redirect jungle until the file arrives:

$ wget http://mbirth.de/keybase.txt
--2014-04-12 00:50:31--  http://mbirth.de/keybase.txt
Resolving mbirth.de (mbirth.de)... XXX ...
Connecting to mbirth.de (mbirth.de)|XXX|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.mbirth.de/keybase.txt [following]
--2014-04-12 00:50:31--  http://www.mbirth.de/keybase.txt
Resolving www.mbirth.de (www.mbirth.de)... XXX
Connecting to www.mbirth.de (www.mbirth.de)|XXX|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://www.mbirth.de/keybase.txt?attredirects=0 [following]
--2014-04-12 00:50:31--  http://www.mbirth.de/keybase.txt?attredirects=0
Reusing existing connection to [www.mbirth.de]:80.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://12345678-a-62cb3a1a-s-sites.googlegroups.com/site/mbirth/keybase.txt?attachauth=ANoREALLYBIGAUTHKEY%3D%3D&attredirects=0 [following]
--2014-04-12 00:50:31--  http://12345678-a-62cb3a1a-s-sites.googlegroups.com/site/mbirth/keybase.txt?attachauth=ANoREALLYBIGAUTHKEY%3D%3D&attredirects=0
Resolving 12345678-a-62cb3a1a-s-sites.googlegroups.com (12345678-a-62cb3a1a-s-sites.googlegroups.com)... XXX
Connecting to 12345678-a-62cb3a1a-s-sites.googlegroups.com (12345678-a-62cb3a1a-s-sites.googlegroups.com)|XXX|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://12345678-a-62cb3a1a-s-sites.googlegroups.com/site/mbirth/keybase.txt?attachauth=ANoREALLYBIGAUTHKEY%3D%3D&attredirects=0 [following]
--2014-04-12 00:50:31--  https://12345678-a-62cb3a1a-s-sites.googlegroups.com/site/mbirth/keybase.txt?attachauth=ANoREALLYBIGAUTHKEY%3D%3D&attredirects=0
Connecting to 12345678-a-62cb3a1a-s-sites.googlegroups.com (12345678-a-62cb3a1a-s-sites.googlegroups.com)|XXX|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘keybase.txt.1’

    [ <=>                                                                                                                                                                                                                            ] 1.983       --.-K/s   in 0s      

2014-04-12 00:50:32 (6,05 MB/s) - ‘keybase.txt.1’ saved [1983]

And keybase doesn't seem recognize the file.

Shortly after verifying my github account, I received this banner message at the top of my screen on all pages.

Just thought you would want to know.

How do we remove proofs? I'm trying to remove a DNS proof, and I don't think the commandline or website offers that.

The key_id field in key sections signed by PGP keys isn't really used for anything, but we still require it. Should we remove it completely?

Thanks to google plus, should be pretty easy to check google accounts too.

I hope to see them checkable soon :)

Copied from https://twitter.com/EdOverflow/status/954093588362809345 (in which see further details):

I claimed ownership of http://liberapay.com on Keybase by creating a user called "keybase.txt" and placing the verification snippet in the profile's description.

Would love to see this =)

Ricochet IM, as you may have noticed, is quickly becoming the new standard for communication of those with high needs in privacy. It would be awesome to verify my identity on there as well.

Can't post a text or change DNS, but can make posts ala Twitter.

I am moving this request from the client issues tracker.

I have a private twitter feed, so I tried putting the proof into the twitter profile (visible on the twitter.com/@user page). That should be recognized as well as it being in the feed, but it isn't.

(I did try changing my privacy setting to public, tweeting the proof, doing the verification (which worked), and then returning to private; but once I did the latter the proof broke.)

Note that another user is using tweetdelete.net to delete his tweets after 10 days, which forces him to redo his proof every 10 days.

Change Verifier::_check_json; most of those checks are now being done in unbox in kbpgp.

See keybase/kbpgp#54 for more details about this refactor.

Here's my proof: https://www.reddit.com/r/KeybaseProofs/comments/2qq3a4/my_keybase_proof_redditlaserlemon/

Keybase can't seem to verify. Thank you!

This should be part of _v_check. Codify the possibilities in the library.

CC: @lord @oconnor663

keybase id --skip-proof-cache
▶ INFO Identifying paulhugel
✔ public key fingerprint: D922 B7B1 3A4D 9BF9 0927 DCA1 7A14 4B7D A3F4 8305
฿ bitcoin 1KbKNUaZFwF7s9j3UNLaPycPvYgoSqwuFW
✔ admin of DNS zone nko.org: found TXT entry keybase-site-verification=lCQtHEPPWQAyyAZLOxbIeUQxdYO4EIIxqo_vswfRsB8
✔ "paulhugel" on github: https://gist.github.com/8e3ae3921cc2e7c89e0d
✔ "paulhugel" on hackernews: https://news.ycombinator.com/user?id=paulhugel
✔ admin of paulhugel.keybase.pub via HTTPS: https://paulhugel.keybase.pub/keybase.txt
✔ "paulhugel" on twitter: https://twitter.com/paulhugel/status/588158776471003136
✔ "paulhugel" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/32n9ej/my_keybase_proof_redditpaulhugel_keybasepaulhugel/
✔ admin of nko.org via HTTPS: https://nko.org/keybase.txt
✔ "paulghugel" on facebook failed: API network error: Get https://www.facebook.com/paulghugel/posts/698602107008518: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) (code=170)
Pauls-MacBook-Air:~ paul$
Pauls-MacBook-Air:~ paul$
Pauls-MacBook-Air:~ paul$ keybase version
Client: 1.0.21-20170413194757+9dea6e1
Service: 1.0.21-20170413194757+9dea6e1

In support of keybase/keybase#204

And also we should rename the virtual methods that SubkeyBase requires to be prefixed with _v_ for consistency. Sorry I blew this.

Hey, i have this graph:

I want to perform the changes marked in red.

How can these changes be done, and where is the interface for this documented?

As per keybase/client#544, there should be a dedicated link for PGP updates, just to capture the new pgp_full_sha256 hash.

The Keybase server claims not to be able to verify the proof for https://www.owlfolio.org/ since May 16. Nothing has changed on my site, and I can manually verify (with a web browser) that https://www.owlfolio.org/.well-known/keybase.txt still exists and its contents are unchanged since I put it there quite some time ago. When I tell the Keybase server to retry the proof, it immediately tells me that the proof still fails. The access logs for my site indicate that keybase-proofs/2.1.11 has not even tried to download the proof since May 16. What might be wrong?

Please add support for verifying one's self on tootsuite/mastodon instances.

There's no reason to do the scraping for hunting for the tweet ID, since we can use the Twitter API for that.

But for now, it works with the scrapar, so let's keep it that way.

In particular the newline won't be in the whitelisted ASCII Set.

https://gitlab.com/

To prove a Flickr identity (or other photo sharing services), could the signed JSON be encoded into a QR code image, or is that too tricky?

I want to verify https://kæn.guru as my domain, but it is not accepted in the input field.

As per keybase/client#544, add new field full_pgp_sha256 to applicable eldest, dualkey and sibkey chainlinks.

Atlassian Bitbucket launched their Snippets feature today which allows developers to post arbitrary pieces of code publicly. With the addition of this feature, users should now be able to create Bitbucket proofs.

Documentation for the API is available here: https://confluence.atlassian.com/display/BITBUCKET/snippets+Endpoint

Gravatar is the public profile service for all WordPress.com users.

I'm employed by Automattic, (the company behind WordPress.com and Gravatar) I think we could reasonably add a spot for our users to add a Keybase verification signature.

It would be great to be able to link an eBay account to keybase.

It's become quite common to expect everyone to be using Github. A lot of people prefer Bitbucket (or a private repo, those can be validated as websites) and it would be nice to have support for that as well :)

If keybase would let users add an ethereum adress, it could be used to verify the identity on the ethereum blockchain using oracle services like oraclize.
This would help a lot of smart contracts that would require a reputation system, for example querying reddit post karma, etc to provide a somewhat working proof-of-individuality

How this would work:
User adds ethereum adress
User calls contract with ethereum adress
Contract calls oraclize (or other oracle)
Oraclize calls keybase
Oraclize returns adress to contract
Contract can call oraclize to determine scoring using keybase data

A proof of address ownership could be made using a keybase contract on ethereum, if you want to verify it. It could be accessed using INFURA if you don't want to keep in sync with the ethereum chain.

Right now we're scraping from keybase-proofs subreddit, but it might be easier to scrape on the per-user page. In v2.0.26, we pushed some temporary bugfixes to crashers, but we should do the right thing and fix and simplify our strategy.

As part of keybase/keybase-issues#367

Reduce the proliferation of tags, since a lot of times these sig types accompany one another.

Did I screw something up here?

https://keybase.io/kevinsuttle
http://kevinsuttle.com/keybase.txt

This will break many existing non-released software components.

(the proofs should look more or less the same)

Why don't prove also facebook, like this: [email protected]:keybase/proofs.git :-)

For keybase/client#379

• maybe factor out some code