REVOCABLE IDENTITY-BASED BROADCAST PROXY RE-

ENCRYPTION FOR DATA SHARING IN CLOUDS

By
BODIGE BHARATHWAJ GOUD (18WJ1A0557)
AMANAGANTI HEMANTH BABU (18WJ1A0516)
BORRA BHARATH KUMAR(18WJ1A0560)

Under the Esteemed Guidance of

Dr. J. Rajeshwar (Professor & HOD CSE)

Guru Nanak Institutions Technical Campus (Autonomous)

OVERVIEW of the Presentation:-
• Abstract
• Objective
• Introduction
• Literature survey
• Existing System
• Proposed System
• System Architecture
• UML and Data Flow Diagrams
• Screenshots
• Conclusion
• Future Enhancements
ABSTRACT:

Cloud computing has become prevalent due to its nature of massive storage and vast
computing capabilities. Ensuring a secure data sharing is critical to cloud applications.
Recently, a number of identity-based broadcast proxy re-encryption (IB-BPRE)
schemes have been proposed to resolve the problem. However, the IB-BPRE requires
a cloud user (Alice) who wants to share data with a bunch of other users (e.g.
colleagues) to participate the group shared key renewal process because Alice’s private
key is a prerequisite for shared key generation. This, however, does not leverage the
benefit of cloud computing and causes the inconvenience for cloud users.
ABSTRACT:

Therefore, a novel security notion named revocable identity-based

broadcast proxy re-encryption (RIB-BPRE) is presented to address
the issue of key revocation in this work. In a RIB-BPRE scheme, a
proxy can revoke a set of delegates, designated by the delegator, from
the re-encryption key. The performance evaluation reveals that the
proposed scheme is efficient and practical.
OBJECTIVE:

• To introduce an identity-based broadcast proxy re-encryption mechanism with

revocation on delegated recipients.

• To allowing the sharing functionality on encrypted cloud data and revocation

on delegated recipients.

• To ensure secure data storage in cloud with the implementation of Public

Cloud mechanism.

• To ensure a secure data sharing to cloud applications.

INTRODUCTION:
• Cloud computing has been suffering from security and privacy challenges.

• Encryption can be a straightforward approach to ensure data confidentiality and Identity-based

encryption (IBE) is one of the promising representative secure mechanisms because it has a concise
public key infrastructure.

• For example, a set of volunteers upload their genome data to the cloud in a genome record cloud
system for the scientists to collaboratively conduct medical research.

• If IBE is adopted into such a medical system, the genome data should be encrypted before uploading
to the cloud as Enc(m; id), where m is the genome data and id is the recipient’s identity.

• A researcher Alice with the identity id from the genome research institute may want to share the
volunteer’s genome data with a list of her colleagues with identities id1,id2,id3,idn in the same
research group.
LITERATURE SURVEY-I:
Title : Identity-based proxy Re-encryption
Author : M. Green and G. Ateniese
Description :
In a proxy re-encryption scheme a semi-trusted proxy converts a cipher text for Alice
into a cipher text for Bob without seeing the underlying plaintext. A number of
solutions have been proposed in the public-key setting. In this paper, we address the
problem of Identity-Based proxy re-encryption, where cipher texts are transformed
from one identity to another. Our schemes are compatible with current IBE
deployments and do not require any extra work from the IBE trusted-party key
generator. In addition, they are non-interactive and one of them permits multiple re-
encryptions. Their security is based on a standard assumption (DBDH) in the random
oracle model
LITERATURE SURVEY-II:
Title : An identity based encryption scheme based on quadratic residues
Author : C. Cocks
Description :

We present a novel public key cryptosystem in which the public key of a subscriber can be
chosen to be a publicly known value, such as his identity. We discuss the security of the
proposed scheme, and show that this is related to the difficulty of solving the
quadraticresiduosity problem
EXISTING SYSTEM:
• Although existing IB-PRE and IB-BPRE schemes can practically address the drawbacks of IBE
in cloud data sharing, they are not suitable to solve the problem of revocation.
• Revocation is very important since we should protect the volunteers’ genome data from
unauthorized users.
• This, therefore, motivates us to discover a new identity-based mechanism that supports to easily
share outsourced encrypted data and sharing revocations.
• Thus, a delegatee colluding with the proxy can not reveal Alice’s private key. However, their
scheme can not achieve the revocation functionality.
EXISTING SYSTEM DISADVANTAGES:-
• Can’t achieve the key revocation functionality.
• It is lacking of the flexibility of data sharing.
• Re-encrypt the records with identities in the sharing list process brings a lot of extra burden
PROPOSED SYSTEM:
• An identity-based broadcast proxy re-encryption mechanism with revocation on delegated
recipients allows the sharing functionality on encrypted cloud data and revocation on
delegated recipients.
• We present a RIB-BPRE construction and prove it is semantic secure in the random model.
Additionally, the evaluation demonstrates that our scheme is efficient and practical in terms of
performance.
• Therefore, the challenge is how to implement a medical research system to support the
researchers to share the extremely sensitive genome data among them without disclosing any
private information from volunteers.
PROPOSED SYSTEM ADVANTAGES:-
• This is achieve the revocation functionalities.
• This is Efficient and practical
• Resolved the issue of key revocation for data sharing
SYSTEM ARCHITECTURE:
Checks Available Data Given all authorities
Login Owner,User & PS Details
Display all Users
Generate & Ps details
CA authority file

Cloud Authority Display all Data Owner,User & PS details

Proxy Server

Register / Login Upload Files Appliying Revocable and Decentralized Attribute-Based

Encryption Algorithm

Data Owner
Generate Original CipherText(CT) Secret Key & Re-encrypted key Generated by Proxy Server

View Files Req For Secret Key Req For Re-encrypted trapdoor key

User Download Original Decrypt CT

USE CASE DIAGRAM:
View files by ABE Reg/Login

secret ker res upload files

Alice
proxy reencrypted view upload
cloudserver

Reg/Log
trapdoor req & res

view files
cloud log
Database

search

view bobs
Bob
req secret key

secret ker req & gen

Req & resSecret key

proxy server
view alices
Req & res trapdoor

trapdoor req & per

view files MD
SEQUENCE DIAGRAM:
Cloud Server Proxy Server Alice Bob Databse

Req/Log

View All Files by ABE

Secret Key Res

Proxy Re-encrypted

Trapdoor Req & Res

time delay
view File Score Res
Rweg/log

View Alices & Bob

View files MD
Secret Key Req & generate
View Trapdoor Req

Reg/log
upload files
view Upload

Reg/log

view files
Req secret key
Req trapdoor permission
view Trapdoor res
E-R DIAGRAM
DATA FLOW DIAGRAM

Register

Login Data base

Verify
Home Page Details Error page
SYSTEM REQUIREMENTS
• SOFTWARE REQUIREMENTS
• FRONT END : J2EE (JSP, SERVLET)
• BACK END : MY SQL 5.5
• OPERATING SYSTEM : WINDOWS 7
• IDE : ECLIPSE

• HARDWARE REQUIREMENTS
• PROCESSOR : DUAL CORE 2 DUOS.
• RAM : 2GB DD RAM
• HARD DISK : 250 GB
Screenshot - 1: Bob Page (Registration)
Screenshot - 2: Registration
Screenshot - 3 : Alice Page (Data Provider Login)
Screenshot - 4: Data Provider Account Page
Screenshot - 5: File Encryption Page
Screenshot - 6: Proxy Server to generate keys
Screenshot - 7: Proxy Server Account
Screenshot - 8: Generation of keys
Screenshot - 9: Key generation to get private keys
Screenshot - 10: Private Cloud Login Page
Screenshot - 11: Private Cloud Account Page
Screenshot - 12: Public Cloud Login Page
Screenshot - 13: Public Cloud Account Page
Conclusion
• We defined revocable identity-based broadcast proxy re-encryption, proposed a
concrete construction under the definition and proved our scheme is CPA secure in
the random oracle model. More importantly, the property and performance
comparison reveals that our proposed scheme is efficient and practical.

• Furthermore, our RIB-BPRE scheme can nicely support key revocation for a data
sensitive system in a cloud environment, for example, a volunteer based genome
research system. While this work has resolved the issue of key revocation for data
sharing, it motivates some interesting open problems such designing RIB-BPRE
scheme without random oracles and how to support more expressive on identities
Future Enhancement

In this project, only text files are getting encrypted for storing files in
cloud. But, we can implement encryption for all kinds of files. If this is
possible, all kind of files like document,audio,video etc files can also be
encrypted. So, secure data sharing can be achived for all kinds of files.
Revocable Identity based broadcast proxy re-encryption can be
achieved for all kinds of files.
Any Queries?

Thank You