Full Disclosure mailing list archives
Re: keybase.io
From: "Dennis E. Hamilton" <dennis.hamilton () acm org>
Date: Sat, 21 Jun 2014 13:01:46 -0700
-----Original Message----- From: Rikairchy Sent: Friday, June 20, 2014 13:22 [ ... ] There is an option to create as well as upload your private key. I'm very new to this type of encryption, having only worked with Truecrypt, SSH, and Bitloccker prior, but I was under the impression that the private key was the last thing you should part with. Why would a website focused on providing security allow users to upload their private keys? <orcnote> It is not necessary to store the private key at keybase.io. I have Not done so. When the private key is at keybase.io, it is in an Encrypted form for which keybase.io does not have the key. If users Want to operate in the browser, instead of the client, there needs To be a way to apply the private key there, and that is only when the one at keybase.io is needed. Just the same, I see no reason for adding to my private key's "threat surface" by having a copy of it at keybase.io. </orcnote> As mentioned, there are github, twitter, and website ownership verification options, tied to your GPG public key. This does no more than verifies that someone that has access to @username on twitter and example.net (which are both listed on a user's keybase.io profile) are controlled by the same person, but not the identity of said person, correct? <orcnote> Correct. The keybase.io schemes associates identifiers of various Kinds with proofs that someone with authority over the private key Made the verified claims. In my case, you can see by my public key at <https://people.apache.org/keys/committer/orcmid.asc>, <http://keybase.io/orcmid>, or your favorite PGP key server that I Have also achieved email verification via the PGP Global Registry. </orcmid> I also have keybase.io invites if this interests anyone. <orcnote> Me too. - Dennis E. Hamilton dennis.hamilton () acm org +1-206-779-9430 https://keybase.io/orcmid PGP F96E 89FF D456 628A </orcmid> _______________________________________________ Sent through the Full Disclosure mailing list http://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: http://seclists.org/fulldisclosure/ _______________________________________________ Sent through the Full Disclosure mailing list http://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: http://seclists.org/fulldisclosure/
Current thread:
- keybase.io Rikairchy (Jun 21)
- Re: keybase.io Dennis E. Hamilton (Jun 22)
- Re: keybase.io Attilla de Groot (Jun 22)
- Re: keybase.io Tony Arcieri (Jun 22)
- Re: keybase.io Robert Dannhauer (Jun 22)
- Re: keybase.io Tony Arcieri (Jun 23)
- Re: keybase.io Jonathan Care (Jun 23)
- Re: keybase.io Tony Arcieri (Jun 25)
- Re: keybase.io Tony Arcieri (Jun 23)
- Re: keybase.io Sam Stewart (Jun 25)
- Re: keybase.io Nick Boyce (Jun 23)