Re: Forge Project proposal: PSE-ABC
Daniel Brookshier <[email protected]> Tue, 13 Jun 2006 08:34:04 -0500
| Newsgroups | gmane.comp.java.jxta.user |
|---|---|
| Message-ID | <[email protected]> |
+1 Daniel Brookshier office 972-422-5261 cell 214-207-6614 On Jun 12, 2006, at 10:36 AM, Vanessa Williams wrote: > We certainly need a good example of how to use the PSE stuff. I get =20= > requests for help all the time (sadly, I have almost none to give.) =20= > Whether it should be a separate project or not, I leave to others =20 > more familiar with what should and should not go into the =20 > programmer's guide. Perhaps it could be an expanded tutorial? With =20 > the code eventually contributed to commons? Just thoughts... > > Vanessa > > On 12-Jun-06, at 10:49 AM, Bruno Margerin wrote: > >> Hi, >> >> I would like to propose a modest =93forge level=94 project about PSE =20= >> security. This project (PSE-ABC) aims at providing the ABC of the =20 >> PSE Membership, hence to lower the learning curve of using the =20 >> basics of PSE Membership. The project's goal is to provide easily =20 >> re-usable and/or copy/pastable code and documentation for a =20 >> typical PSE Membership use. >> >> The code will provide examples for both basic certificates / =20 >> private key usage as well as of use more JXTA specific =20 >> technologies such as PSE membership, TLS and Access Control. >> >> Specifically for Certificates manipulation: >> =95 Issuing a self signed certificate authority >> =95 Issuing a =93SuperPeer=94 / Administrator Certificate/PKey, = having =20 >> the CA sign the associate signing request, and import the =20 >> resulting signed certificates back. >> =95 Issuing 2 edges peers (Peer A and Peer B) Certificates/PKeys and =20= >> have the SuperPeer / Administrator sign the signing request and =20 >> the edge peers import the resulting signed certificates. >> =95 Manage associated Keystores and associated chains of trust on =20 >> each 4 entities (CA, Super/Administrator Peers, and the 2 edge =20 >> peers). >> >> For simplicity, while using the JXTA utils, this initial security =20 >> infrastructure will be build =93off line=94, not using the JXTA =20 >> platform. I don=92t aims at implementing any distributed trust model =20= >> such as JXTA Poblano for instance. Again the goal of this project =20 >> is to introduce PSE Membership. >> >> As for the PSE Membership and associated technologies, the =20 >> scenario would be to: >> =95 Have the Super Peer create/publish and join a PSE Peer Group. >> =95 Have the 2 Edge Peers (Peer A and Peer B) join this group. >> =95 Have an Edge Peer (Peer A), create an access controlled JXTA =20 >> Socket where Peer B would connect via TLS. The access control =20 >> mechanism would be an =93all or nothing=94 access based and whether =20= >> Peer A and Peer B has =93common roots=94 in their chain of trust. >> >> I first though that such an example could be contributed within =20 >> the JXTA programmer=92s guide, but given the expected volume of =20 >> code, I am now thinking that it may make the guide overly heavy =20 >> and need to be taken outside the guide, as a separate project/=20 >> tutorial. >> >> I am neither a JXTA nor a security expert and would rely on the =20 >> community for ensuring that I am understanding and using the =20 >> security and JXTA tools correctly and to best practices. >> >> Last, I would also appreciate feed back in whether or when this =20 >> forge project should be integrated in the JXTA commons. >> >> Please let me know what you think, >> Thanks, >> >> Bruno Margerin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > -- > Vanessa Williams > Oponia Networks > [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >