search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Accept private gist URLs to verify via a private gist #186

Open jasonkarns opened 10 years ago

tildelowengrimm commented 10 years ago

If a gist is private, how can someone else verify it?

jasonkarns commented 10 years ago

To access a private gist, all you need is the URL.​ They aren't authenticated or protected in any way.

malgorithms commented 10 years ago

hmm, interesting! I didn't know that! (I should've moused over the private button, I see that now.)

There's no need for the gist to be public from our perspective - even as a promotional vehicle for either keybase or your identity. I guess there are some advantages to these things being discoverable in the default case - SEO for your own key, keybase, etc., but heck, it's not like anyone goes around surfing gists. It might as well be up to you.

I think my only reservation would be to avoid adding extra steps. It's nice that we find the gist for you, keeping the interface simple. One possibility is we just ask you to post the gist, then we look for it, and if we can't find it, we ask you to give us the URL. This serves the secondary purpose that if there's a problem with the proof for some reason, we can debug it easily. So we should be doing this anyway.

malgorithms commented 10 years ago

(btw, to both of you: I appreciate all the issues/comments on all these issues. I'm looking forward to Max returning tomorrow so we can go over everything together.)

jasonkarns commented 10 years ago

Yeah, I agree with the secondary purpose (if something goes wrong with the auto-find). The autofind actually was weird for me. I started via the command line, exited the interactive loop while I uploaded the gist (still wish I could have done that via the gist brew package). Then I expected that I would have to manually tell keybase that I was finished uploading. (Since I had killed the interactive confirm loop) So I was poking around for a way to force-recheck of github when I saw on my profile that it had already been found. A little confusing.

On Sun, Mar 9, 2014 at 3:28 PM, Chris Coyne notifications@github.comwrote:

(btw, to both of you: I appreciate all the issues/comments on all these issues. I'm looking forward to Max returning tomorrow so we can go over everything together.)

— Reply to this email directly or view it on GitHubhttps://github.com/keybase/keybase-issues/issues/186#issuecomment-37136147 .