MABS Multicast Authentication Based On Batch Signature.doc (Size: 181 KB / Downloads: 647)
1. Data integrity: Each receiver should be able to assure that received packets have not been modified during transmissions.
2. Data origin authentication: Each receiver should be able to assure that each received packet comes from the real sender as it claims.
3. No repudiation: The sender of a packet should not be able to deny sending the packet to receivers in case there is a dispute between the sender and receivers.
All the three services can be supported by an asymmetric key technique called signature. In an ideal case, the sender generates a signature for each packet with its private key, which is called signing, and each receiver checks the validity of the signature with the sender’s public key, which is called verifying. If the verification succeeds, the receiver knows the packet is authentic. Designing a multicast authentication protocol is not an easy task. Generally, there are following issues in real world challenging the design. First, efficiency needs to be considered, especially for receivers. Compared with the multicast sender, which could be a powerful server, receivers can have different capabilities and resources.
The receiver heterogeneity requires that the multicast authentication protocol be able to execute on not only powerful desktop computers but also resource-constrained mobile handsets. In particular, latency, computation, and communication overhead are major issues to be considered. Second, packet loss is inevitable. In the Internet, congestion at routers is a major reason causing packet loss. An overloaded router drops buffered packets according to its preset control policy. Though TCP provides a certain retransmission capability, multicast content is mainly transmitted over UDP, which does not provide any loss recovery support. In mobile environments, the situation is even worse.
The instability of wireless channel can cause packet loss very frequently. Moreover, the smaller data rate of wireless channel increases the congestion possibility. This is not desirable for applications like real-time online streaming or stock quotes delivering. End users of online streaming will start to complain if they experience constant service interruptions due to packet loss, and missing critical stock quotes can cause severe capital loss of service subscribers. Therefore, for applications where the quality of service is critical to end users, a multicast authentication protocol should provide a certain level of resilience to packet loss. Specifically, the impact of packet loss on the authenticity of the already-received packets should be as small as possible. Efficiency and packet loss resilience can hardly be supported simultaneously by conventional multicast schemes.
Single cast authentication based batch signature related tool is available where the user can send the file without encrypting and decrypting the file. So here there will not be any security while the user is transforming the files in between different intermediate nodes. so user is looking for proposed system where more security is incorporated and adopted.
Here the data is encrypted and decrypted in the for of matrix and engineering. While data is decrypting in server side it is reverse engineering in the format of original data. So here digital signature is also verified and the receiver is multicasting by the sender so that the receiver can receive ‘N’ number of files at a time from different senders. So here we are enforcing the more security on the system.
Algorithms Used :
1. Core Resolution Algorithm - Encryption and Decryption
2. Batch RSA Algorithm - Bath Signature
3. Optimal MABS Router Protocol – File Transfer
1. Digital Certificate - Authentication and Authorization
Processor : Pentium-IV
Speed : 1.1GHz
RAM : 512MB
Hard Disk : 40GB
General : Keyboard, Monitor, Mouse
Operating System : Windows XP
Software : JAVA (JDK 1.6.0)
Protocol : TCP/IP
IDE : Eclipse
Front End : Java Swing