Received: by 10.50.213.99 with SMTP id nr3mr8889581igc.2.1350870217881; Sun, 21 Oct 2012 18:43:37 -0700 (PDT) X-BeenThere: android-developers@googlegroups.com Received: by 10.42.244.193 with SMTP id lr1ls8597761icb.1.gmail; Sun, 21 Oct 2012 18:40:59 -0700 (PDT) Received: by 10.50.173.68 with SMTP id bi4mr4684015igc.1.1350870059658; Sun, 21 Oct 2012 18:40:59 -0700 (PDT) Received: by 10.50.173.68 with SMTP id bi4mr4684014igc.1.1350870059649; Sun, 21 Oct 2012 18:40:59 -0700 (PDT) Return-Path: Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by gmr-mx.google.com with ESMTPS id s9si740450igw.0.2012.10.21.18.40.59 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 21 Oct 2012 18:40:59 -0700 (PDT) Received-SPF: pass (google.com: domain of nikolay.elen...@gmail.com designates 209.85.223.181 as permitted sender) client-ip=209.85.223.181; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nikolay.elen...@gmail.com designates 209.85.223.181 as permitted sender) smtp.mail=nikolay.elen...@gmail.com; dkim=pass header...@gmail.com Received: by mail-ie0-f181.google.com with SMTP id 16so3201409iea.40 for ; Sun, 21 Oct 2012 18:40:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GIA+jI5Og+4iBtgSAOibhiswGFc6IoxdluCrJbwBVWQ=; b=Q2ZnXkFP5JMYGMlLwblvJXtpMxxfrEwr2y2BY0fEEwSraWRPVxds5NK4f0ynz58Uvc ykeIQpzjIzQ1+++oIn4xGQp45+BqkAnM7/IXnSaf7akBl0By47PolTggdzStE/qQJ4iB CKYukqsfVdzZaqDOSpuPiJ1okxpQ4o5cehs8W78g+9eOe64M7iiIc/Bw1q0vcvrXe3Es Nva3VFYaX2KGR9W6v28lyT4RlSskAKqD/7JZLJQGRbgpH9aWDGLI3F6Qx0TamImvh5O9 d9eVpMQqYBZDB4Av3UschNYlBPgX3rftliCO+m8Ur3Jf2ZCfVITKe+lvdI1yxA2k0R2F z3xw== MIME-Version: 1.0 Received: by 10.50.194.132 with SMTP id hw4mr15039995igc.9.1350870059495; Sun, 21 Oct 2012 18:40:59 -0700 (PDT) Received: by 10.64.46.38 with HTTP; Sun, 21 Oct 2012 18:40:59 -0700 (PDT) In-Reply-To: <0e0f275c-9193-41f5-94ee-f56191dc84f8@googlegroups.com> References: <0e0f275c-9193-41f5-94ee-f56191dc84f8@googlegroups.com> Date: Mon, 22 Oct 2012 10:40:59 +0900 Message-ID: Subject: Re: [android-developers] Creating keys for usage with "KeyChain" From: Nikolay Elenkov To: android-developers@googlegroups.com Content-Type: text/plain; charset=UTF-8 On Thu, Oct 18, 2012 at 1:47 PM, Anders Rundgren wrote: > Google can create keys accessible through KeyChain using the browser and > . > > How can mere mortals do the same thing? > Not sure what exactly you are trying to do. The keystore has interfaces for storing keys (and since JB directly generating), but those are not public. Anyone (i.e., not system-level permission required) can use them though, so the Android browser probably is. Of course if you use them, you risk breaking in the next Android version.