PrivaSphere - project:
<h1>Public Key Server</h1>
<h2>Institution: ZHW</h2>
<h3>Supervisor: Marc Rennhard, Ralf Hauser</h3>
<h3>Team: t.b.d.</h3>
<h2>Background:</h2>
Years ago, a PGP key-server has been built at MIT. For the
S/MIME i.e. x.509 world the landscape is rather fragmented. Some
CA's have a public key directory for their own clients, but no
overarching solution is available and the offered ones are
sometimes of limited implementation quality.<br />
REFERENCE: 10 reasons why PKI fail http://www.schneier.com/paper-pki-ft.txt
http://www.schneier.com/crypto-gram-0112.html<br />
<br />
see also https://www.certbox.org/de/search/
<h2>Goal/Challenges:</h2>
<ul>
<li>Build a public key server for both S/MIME and PGP/GPG.</li>
<li>Provide a simple interface for users to register themselves</li>
<li>Offer a LDAP interface for end-users and peer directories</li>
<li>In view of lack of endorsement of public key certificates
by government and other institutions as well as due to the lack
of pervasive revocation list functions, allow users to prove they
a still in possession of their private key by "encrypted challenges"
and add the result of such challenges (e.g. date of last successful
execution) as optional information to the directory.</li>
</ul>
<hr />
<h2>General Requirements</h2><ul>
<li>
use a version control system (recommendation: git, svn)
</li>
<li>
use an open source license(recommendation: Berkeley, Apache)
</li>
<li>
use a modern, platform independent implementation technology (e.g. Java) / Java Skills
</li>
<li>
use a modern quality assurance tool (justify if anything other than
BugZilla)
</li>
</ul>
<h2>PrivaSphere Role</h2><ul>
<li>be a tutor; as well as a design, architecture, and technology
discussion partner</li>
<li>provide space for a project-"product" in our BugZilla for
quality assurance service and temporary SVN server space</li>
</ul>