28-07-2012, 10:33 AM
Authenticated Group Key Transfer Protocol Based on Secret Sharing
Group Key Transfer.doc (Size: 279 KB / Downloads: 59)
Abstract
Key transfer protocols rely on a mutually trusted key generation center (KGC) to select session keys and transport session keys to all communication entities secretly. Most often, KGC encrypts session keys under another secret key shared with each entity during registration. In this paper, we propose an authenticated key transfer protocol based on secret sharing scheme that KGC can broadcast group key information to all group members at once and only authorized group members can recover the group key; but unauthorized users cannot recover the group key. The confidentiality of this transformation is information theoretically secure. We also provide authentication for transporting this group key. Goals and security threats of our proposed group key transfer protocol will be analyzed in detail.
SYSTEM ANANLYSIS
Existing System
The existing system involves centralized key server in which all the systems depend on centralized key server for key generation. All the members depend on the centralized key server for key generation. Re keying, which means renewing the keys associated with the nodes of the key tree, is performed whenever there is any group membership change including any new member joining or any existing member leaving the group. This individual re keying operation increases the computation and communication cost. More resources have been utilized by the server in case of multiple join and leave of members in the group. For every individual re keying operation which is happening for single join and leave operation all the group members depends on the centralized key server for group key generation.
Proposed System
The proposed system involves authenticated Key agreement in which all nodes become a part of the group key. The group key is generated which is common for all the members in the group. The communication in the group is done with the help of the group key. The members can communicate with other members such as sending files to other members with the help of the group key. Instead of performing individual re keying operations, i.e., re computing the group key after every join or leave request, we are going to re key for a batch of join operations. Moreover, re keying is done after a batch of join or leave operations. We consider interval-based distributed re-keying algorithms, or interval-based algorithms for short, for updating the group key:
COMPONENTS OF . NET FRAMEWORK
THE COMMON LANGUAGE RUNTIME (CLR):
The common language runtime is the foundation of the .NET Framework. It manages code at execution time, providing important services such as memory management, thread management, and remoting and also ensures more security and robustness. The concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code.
FEATURES OF THE COMMON LANGUAGE RUNTIME:
The common language runtime manages memory; thread execution, code execution, code safety verification, compilation, and other system services these are all run on CLR.
• Security.
• Robustness.
• Productivity.
• Performance.
SECURITY
The runtime enforces code access security. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally feature rich. With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin to perform file-access operations, registry-access operations, or other sensitive functions.
ROBUSTNESS:
The runtime also enforces code robustness by implementing a strict type- and code-verification infrastructure called the common type system(CTS). The CTS ensures that all managed code is self-describing. The managed environment of the runtime eliminates many common software issues.
PRODUCTIVITY:
The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers.
PERFORMANCE:
The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS).
VISUAL STUDIO .NET:
Visual Studio .NET is a complete set of development tools for building ASP Web applications, XML Web services, desktop applications, and mobile applications In addition to building high-performing desktop applications, you can use Visual Studio's powerful component-based development tools and other technologies to simplify team-based design, development, and deployment of Enterprise solutions.
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixed-language solutions. In addition, these languages leverage the functionality of the .NET Framework and simplify the development of ASP Web applications and XML Web services.
.COMMON LANGUAGE SPECIFICATION (CLS):
Visual Basic.NET is also compliant with CLS (Common Language Specification) and supports structured exception handling. CLS is set of rules and constructs that are supported by the CLR (Common Language Runtime). CLR is the runtime environment provided by the .NET Framework; it manages the execution of the code and also makes the development process easier by providing services.
Visual Basic.NET is a CLS-compliant language. Any objects, classes, or components that created in Visual Basic.NET can be used in any other CLS-compliant language. In addition, we can use objects, classes, and components created in other CLS-compliant languages in Visual Basic.NET .The use of CLS ensures complete interoperability among applications, regardless of the languages used to create the application.
IMPLEMENTATION INHERITANCE:
Visual Basic.NET supports implementation inheritance. This means that, while creating applications in Visual Basic.NET, we can drive from another class, which is know as the base class that derived class inherits all the methods and properties of the base class. In the derived class, we can either use the existing code of the base class or override the existing code. Therefore, with help of the implementation inheritance, code can be reused.
CONSTRUCTORS AND DESTRUCTORS:
Constructors are used to initialize objects, whereas destructors are used to destroy them. In other words, destructors are used to release the resources allocated to the object. In Visual Basic.NET the sub finalize procedure is available. The sub finalize procedure is used to complete the tasks that must be performed when an object is destroyed. The sub finalize procedure is called automatically when an object is destroyed. In addition, the sub finalize procedure can be called only from the class it belongs to or from derived classes.