文件列表:

sepp (0, 2009-03-01)
sepp\.classpath (675, 2009-02-28)
sepp\.project (540, 2009-02-28)
sepp\console_chat.cmd (307, 2009-03-01)
sepp\console_chat.sh (308, 2009-03-09)
sepp\key (0, 2009-03-01)
sepp\key\ca (0, 2009-03-01)
sepp\key\ca\ca.csr (1106, 2008-10-20)
sepp\key\ca\ca.key (1679, 2008-10-20)
sepp\key\ca\ca.pem (1354, 2008-10-20)
sepp\key\ca\ca.srl (3, 2008-10-20)
sepp\key\create_signed_peer_certificate.sh (867, 2009-02-04)
sepp\key\iaik-private.keystore (62725, 2008-12-11)
sepp\key\iaik-secret.keystore (57, 2009-02-04)
sepp\key\jks.keystore (63259, 2008-12-09)
sepp\key\pkcs12.keystore (66059, 2008-12-09)
sepp\lib (0, 2009-03-01)
sepp\lib\commons-logging.jar (26388, 2008-10-20)
sepp\lib\iaik_jce_full.jar (854896, 2008-10-20)
sepp\lib\iaik_smime.jar (34285, 2009-02-04)
sepp\lib\log4j-1.2.12.jar (358085, 2008-10-20)
sepp\lib\mysql-connector-java-5.1.7-bin.jar (709922, 2008-10-21)
sepp\lib\sepp.jar (270092, 2009-03-01)
sepp\lib\swing-layout-1.0.2.jar (159096, 2009-02-04)
sepp\log (0, 2009-03-01)
sepp\res (0, 2009-03-01)
sepp\res\.keystore (4945, 2008-10-20)
sepp\res\log4j.properties (468, 2009-02-28)
sepp\res\peer1.config (2673, 2009-02-28)
sepp\res\peer2.config (2611, 2009-02-28)
sepp\res\peer3.config (2611, 2009-02-28)
sepp\res\peer4.config (2611, 2009-02-28)
sepp\res\peer5.config (2611, 2009-02-28)
sepp\res\peer6.config (2611, 2009-02-28)
sepp\res\peer7.config (2624, 2009-02-28)
sepp\src (0, 2009-03-01)
sepp\src\demo (0, 2009-03-01)
sepp\src\demo\examples (0, 2009-03-01)
sepp\src\demo\examples\chat (0, 2009-03-01)
... ...

****************************************************************** * Secure P2P framework (SePP) (v0.1.3) * ****************************************************************** SePP is a secure P2P framework which allows application developer to create secure distributed components in a simple manner. The framework provides not only the typical management and communication features but also the relevant security features (e.g.: digital signatures, encryption, authentication, ...) using state-of-the-art cryptographic primitives and algorithms. The secure P2P framework also copes with security issues right from the start of the P2P network, allowing only legitimate peers to take part in the network through a secured join process. Another very relevant security feature of this framework is the availability of secure routing algorithms. One can choose between different routing algorithms depending on the use case of the developed application. The whole secure P2P framework has been developed with a coherent and comprehensive security concept in mind which allows the application developer and network designer to exactly specify the security requirements of the application and network. Thus, all the potential peers must comply to this requirements to take part in this network. ------------------------------------------------------------------ In the root directory of this package there exist two simple scripts which can be used to start a simple demo application. The demo application features a chat client with a simple GUI. There exists a version for Windows- and Linux-based systems. The application is started by executing this script and providing a number as parameter. This number relates to the peer configuration which should be used to start this client. For simplicity reasons the peers are named "peerX" where the X denotes the number of the peer. Therefore, the peer1.config in the "res" directory is the configuration file for peer1 and so on. Therefore, for starting peer1 one would execute the following command. start_chat 1 Currently, there are 6 configuration files in the directory which means that only 6 different peers can be started now. The current configuration specifies that all peers are started on the local host and listen on different ports. If one wants to run them on different hosts the according configuration files must be adjusted. There is also a mechanism implemented to find peers in the local network but it has not been tested very seriously. Therefore, it is recommended to use this framework in the current version only with peers specified in their associated configurations and with the parameter "RunLocal" set to true. In upcoming versions this mechanism will be available. In this version also support for storing messages sent and received at the peers and errors produced during processing of these messages in a database has been added. In the config file there are some parameters for configuring the database support. - True or false for storing data in the database. - Specifies the URI of the database as used by JDBC - User name for the database access - Password for the specified database user If you have any other questions either consult the included Java documentation, visit the project home page and its WIKI on http://sourceforge.net/projects/securep2p/ or contact me through securep2p@iaik.tugraz.at Good luck and much fun, Stefan Kraxberger Institute of Applied Information Processing Graz University of Technologoy, Graz, Austria ------------------------------------------------------------------ Change log ------------------------------------------------------------------ v0.1.3 (February 2009) - AriadneRouting has been integrated and tested. Now it should work almost properly. Some modifications must still be made because no improvements to Ariadne have been implemented so far. - The route error handling and invocation of DSR have been modified since some problems have been reported. Now route error should work as described in the RFC. At this point none of the improvements for DSR have been implemented but are now scheduled. - Modified the neighbor algorithm and made some simplifications of the whole communication code. v0.1.2 (November 2008) - Modified the routing algorithm DSR to be compliant with the original version and support route replies from intermediate hosts to allow for faster route discovery. - Modifications of the route cache instantiation to allow different kinds of caching strategies and architectures. Currently the simplest one, the Path Cache, is implemented. - Removed some bugs in the message processing mechanism. v0.1.1 (September 2008) - Modified the process of discovering new peers. Previously it wasn't possible that peers become neighbors which havn't been specified as neighbors in the configuration mutually. Now peers must not specify each other as neighbors to become neighbors during runtime. - Some problems with the reachability of peers have been solved. Still, the process isn't completely reliable yet. - Modified the DSR routing algorithm, due to some problems with creating routes from already existing routes in intermediate peers.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：