Received: by 10.58.254.39 with SMTP id af7mr4215735ved.41.1349646348297;
        Sun, 07 Oct 2012 14:45:48 -0700 (PDT)
X-BeenThere: joomla-dev-platform@googlegroups.com
Received: by 10.52.73.72 with SMTP id j8ls4100133vdv.7.gmail; Sun, 07 Oct 2012
 14:45:47 -0700 (PDT)
Received: by 10.58.169.17 with SMTP id aa17mr4251986vec.29.1349646347398;
        Sun, 07 Oct 2012 14:45:47 -0700 (PDT)
Received: by 10.58.169.17 with SMTP id aa17mr4251985vec.29.1349646347386;
        Sun, 07 Oct 2012 14:45:47 -0700 (PDT)
Return-Path: <mambob...@gmail.com>
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48])
        by gmr-mx.google.com with ESMTPS id r14si929309vdu.1.2012.10.07.14.45.47
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 07 Oct 2012 14:45:47 -0700 (PDT)
Received-SPF: pass (google.com: domain of mambob...@gmail.com designates 209.85.212.48 as permitted sender) client-ip=209.85.212.48;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mambob...@gmail.com designates 209.85.212.48 as permitted sender) smtp.mail=mambob...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-vb0-f48.google.com with SMTP id e21so4345127vbm.35
        for <joomla-dev-platform@googlegroups.com>; Sun, 07 Oct 2012 14:45:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=Kl8AfuwD/oJn2e/ySVbx/je7IEFtqO3eHjj2lV7HVSE=;
        b=UhFOicvaapIq88ybPRwRH54KYEggorsbTe6iF9F+n92pdNB6XesymVhv5tiJ0wf23a
         ah484WnBqj+2eZOgeFAcqTjq9Npd3Yv+DDI4qvg+KN2CPZfUT5l8hu/0rTKC6uNzhkt/
         YlS+lR4ggV3A3rljZILcZRkLKYDHxxa5yXAAQPjpRAf1O3pWjqwrjTXV1dTkjhks9b7w
         8zJOFqt06fpj4WAz7wkg+EhVdfsOxUYiv6FJGEuTbTqYSmHK3ZFHjk77spD7d4TTo/xB
         BB6HI0fSSQPPztQ5Ok8EYhm9SpTa2RfIWaF3O/6wE8J8Wfhprp1YsiQMa8LS2xMVWekq
         PR8g==
Received: by 10.52.71.230 with SMTP id y6mr5235400vdu.82.1349646347241; Sun,
 07 Oct 2012 14:45:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.145.228 with HTTP; Sun, 7 Oct 2012 14:45:26 -0700 (PDT)
From: Andrew Eddie <mambob...@gmail.com>
Date: Mon, 8 Oct 2012 07:45:26 +1000
Message-ID: <CADPtAkSpFySdUhG+fWJbTLhMv0Gd2istr6Ot+-01MOL0sCF...@mail.gmail.com>
Subject: Keychain package
To: JPlatform <joomla-dev-platform@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1

https://github.com/joomla/joomla-platform/pull/1568

OVERVIEW

The keychain provides a way to securely store sensitive information
such as access credentials or any other data. This pull request
contains a new class called JKeychain that extends JRegistry and
supports encrypting and decrypting data through the use of public and
private keys. It also provides the necessary command-line utility (a
Joomla Platform application itself) to generate the key files.

DOCUMENTATION

Documentation is provided in the pull request. A readable version is
available at:

https://github.com/eBaySF/joomla-platform/wiki/Keychain

BUSINESS CASE

At eBay, we needed a way to be able to store sensitive credentials
(server/database logins, etc) in our SCM repository in an encrypted
form without the hassle of sharing those credentials over email or
other electronic means. The Keychain package was developed so we could
store encrypted data in the source code repository (the security
issues related to storing clear-text credentials in a semi-public,
albeit internal, source code repository should be obvious). Engineers
and deployment servers only need obtain the the 'shared key' manually,
but only once. Should the credentials change, the encrypted data file
in the repository simply needs to be updated and all engineers and
servers have access to the new information on the next build.

Regards,
Andrew Eddie