full-disclosure

Open Source and information security mailing list archives

Date: Sat, 21 Jun 2014 13:01:46 -0700
From: "Dennis E. Hamilton" <dennis.hamilton@....org>
To: <fulldisclosure@...lists.org>
Subject: Re: [FD] keybase.io

   -----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@....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/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives