2. INTRODUCTION
AIM OF PROJECT
The mainstay of the project is to collaboratively generate a
common key for peer to peer group communication. To dynamically
perform re-keying operation after batch of joins or leaves using Queue
Batch algorithm and to share resources using the generated group
key.
PURPOSE OF PROJECT
The purpose of the proposed system is to provide the members
of a group with secure common group key. This group key is
generated collaboratively wherein each node becomes a part of the
key generation.
The distributive nature of the proposed system, avoids the usage
of a centralized key server. The dynamic nature of the system allows
the existing members to leave the group while new members can join,
instead of performing individual rekeying operations. The system uses
Queue-batch algorithm for re-keying. The algorithm can substantially
reduce the computation and communication workload in a highly
dynamic environment. The group key is used for future communication
among the members of the group.
2
3. SYTEM ANALYSIS
EXISTING SYSTEM
The existing system involves either centralized key server (in
which all the systems depend on centralized server for key
generation), and individual rekeying is done for join or leave
operations in case of distributive key generation algorithms. In case
of individual re-keying, after every join or leave operation each
member individually rekeys’. More resources are used for re-keying
because it is done for each join or leave operations. In case of using
a centralized server, the risk of single point failure is more.
DRAWBACKS OF EXISTING SYSTEM
•
•
•
Key information depends on centralized key server.
Computational and Communication cost is more.
Individual re-keying is done. Whenever a member joins or
leaves in the case of distributed key generation algorithm.
•
More resources used for re-keying because it is done for each
join or leave operations.
3
4. PROPOSED SYSTEM
The proposed system involves collaborative key agreement in which
all nodes become a part of the secure group key. Moreover,
rekeying is done after a batch of join or leave operations. The
protocol remains efficient even when the occurrences of join/leave
events are very frequent. Here Key information does not depend on
centralized key server. So it is free from the problem of single point
failure. Computational and Communication cost is less. Resources
used for rekeying is minimized because it is being done for batch of
join/leave operations.
4
5. SYTEM REQUIREMENT
HARDWARE REQUIREMENTS
PROCESSOR
:
PENTIUM III 866 MHz
RAM
:
256 MB DD RAM
MONITOR
:
15” COLOR
HARD DISK :
20 GB
FLOPPY DRIVE
:
1.44 MB
CDDRIVE
:
LG 52X
KEYBOARD :
STANDARD 102 KEYS
MOUSE
:
3 BUTTONS
SOFTWARE REQUIREMENTS
LANGUAGE
: JAVA
FRONT END TOOL
: SWING
BACK END TOOL
: SQL SERVER
OPERATING SYSTEM: WINDOWS 98.
5
6. SYTEM REQUIREMENT
HARDWARE REQUIREMENTS
PROCESSOR
:
PENTIUM III 866 MHz
RAM
:
256 MB DD RAM
MONITOR
:
15” COLOR
HARD DISK :
20 GB
FLOPPY DRIVE
:
1.44 MB
CDDRIVE
:
LG 52X
KEYBOARD :
STANDARD 102 KEYS
MOUSE
:
3 BUTTONS
SOFTWARE REQUIREMENTS
LANGUAGE
: JAVA
FRONT END TOOL
: SWING
BACK END TOOL
: SQL SERVER
OPERATING SYSTEM: WINDOWS 98.
5