SCHOOL OF COMPUTING SCIENCES

DEPARTMENT OF COMPUTER APPLICATIONS

A VERIFIABLE CLOUD DATA DEDUPLICATION SCHEME WITH

INTEGRITY AND
DUPLICATION PROOF
A Project Report
Submitted to the VISTAS in partial fulfilment for the award of the degree

of MASTER OF COMPUTER APPLICATION

BY

Name : RISHI N

Reg No : 22304347

Under the guidance of,

Dr. S. ANU PRIYA MCA., M.Phil.,Ph.D Assistant Professor

MAY 2024

i
 SCHOOL OF COMPUTING SCIENCES

DEPARTMENT OF
COMPUTER APPLICATIONS

BONAFIDE CERTIFICATE

This is to certify that the Main Project entitled “A Verifiable and Fair Attribute-
based Proxy Re-encryption Scheme for Data Sharing in Clouds” is the original record by
RISHI N, 22304347, under my guidance and supervision for the partial fulfillment of award
of degree of MASTER OF COMPUTER APPLICATION, as per syllabus prescribed by the
VISTAS.

GUIDE HEAD OF THE DEPARTMENT

Submitted for the Viva-Voce examination held on........................................at

VISTAS Pallavaram, Chennai.

INTERNAL EXAMINER EXTERNALEXAMINER

i
i
 ACKNOWLEDGEMENT
“Let the beauty of the lord fall on us and establish the work of our hands”. At the outset, I
thank the ALMIGHTY GOD for his abundant blessings and for giving me the opportunity to
carry out this project successfully.

I deeply wish to express my sincere thanks to Dr. ISHARI K. GANESH M.Com., B.L.,
Ph.D.,the founder and chancellor of VISTAS, Dr. JOTHI MURUGAN, Pro-Chancellor (P
& D) VISTAS, Dr. ARTHI GANESH, Pro-Chancellor (Academics), Dr. PREETHA
GANESH, Vice-president, Vels Group of institutions.

I extend my thanks to Dr. S. SRIMAN NARAYANAN The Vice-Chancellor, VISTAS for

providing me necessary facilities. I wish to extend my heartfelt and sincere thanks to
Dr.M.BHASKARAN, Pro Vice-Chancellor, VISTAS and sincere thanks to Dr. P.
SARAVANAN, Registrar.

I extend my thanks to Dr. A. UDHAYA KUMAR, Controller of Examinations,

VISTAS. I extend my reverential gratitude to Dr. P. MAGESH KUMAR, Director, School
of Computing Sciences and Dr. R. PRIYA ANAND MCA, M.Phil., Ph.D., and Head of
Department for encouraging me to complete my work. I have extend my deep sense of
gratitude faithfully and sincerely thanks goes to well guide to achieve my project supervisor
of Dr. S. ANU PRIYA MCA., M.Phil.,Ph.D Assistant Professor for helping me with her
support, motivation and guidance throughout this research. Her valuable guidance and
inspiration are the key factors that enabled me to complete this research successfully.

I sincerely express my gratitude’s to MY PARENTS, FRIENDS and our FACULTY

MEMBERS for their continuous prayers, supports and constant encouragement to reach the
heights of success.

Once again, I thank the GOD almighty with whose profound blessings this work has been
completed successfully.

i
 DECLARATION

I am, RISHI N ( 22304347 ) declare that the Main Project entitled “A Verifiable and Fair

Attribute-based Proxy Re-encryption Scheme for Data Sharing in Clouds” is a record of

original work done by me in partial fulfillment of the requirements for the award of the

degree of Master of Computer Application under the gratitude faithfully and sincerely

thanks goes to supervisor of Dr. S. ANU PRIYA MCA., M.Phil.,Ph.D Assistant Professor

for the academic year 2024. This project work has not formed the basis for the award ofany

degree.

(Signature of the Candidate)

v
 ABSTRACT

To manage outsourced encrypted data sharing in clouds, attribute-based proxy re-encryption

(ABPRE) has become an elegant primitive. In ABPRE, a cloud server can transform an
original recipient’s ciphertext to a new one of a shared user’s. As the transformation is
computation consuming, a malicious cloud server may return an incorrect re-encrypted
ciphertext to save its computation resources. Moreover, a shared user may accuse the cloud
server of returning an incorrect reencrypted ciphertext to refuse to pay the cost of using the
cloud service. However, existing ABPRE schemes do not support a mechanism to achieve
verifiability and fairness. In this paper, a novel verifiable and fair attribute-based proxy re-
encryption (VF-ABPRE) scheme is introduced to support verifiability and fairness. The
verifiability enables a shared user to verify whether the re-encrypted ciphertext returned by
the server is correct and the fairness ensures a cloud server escape from malicious accusation
if it has indeed conducted the re-encryption operation honestly. Additionally, we conduct a
performance experiment to show the efficiency and practicality of the new VF-ABPRE
scheme.

v
 TABLE OF CONTENTS
S.
N TITLE PAGE NO
O
ABSTRACT
1. INTRODUCTION
1.1 Company Profile 1

1.2 Project Profile 2

2. SYSTEM ANALYSIS
2.1. Existing System 3

2.2. Proposed System 3

3 SYSTEM REQUIREMENTS
3.1. Hardware Requirements 5

3.2. Software Requirements 5

3.3 Software Description 5

4 SYSTEM DESIGN
4.1. System Architecture 19

4.2. Data Flow Diagram 19

4.3. Component Diagram 20

4.4. Deployment Diagram 20

4.5. UseCase Diagram 21

5 SYSTEM TESTING
5.1. Software Testing 22

5.1.1 - Unit Testing 22

5.1.2 - Integration Testing 22

5.1.3 - Functional test 23

5.1.4 - System Test 23

5.1.5 - White Box Testing 23

v
 5.1.6 - Black Box Testing 24

6. SYSTEM IMPLEMENTATION
6.1. System Description 25

6.2. System Flow 27

6.3. Modules Description 27

7. APPENDICES
7.1. Screenshots 29

7.2. Source code 29

8 CONCLUSION

8.1. Conclusion 45

8.2. Future Enhancement 45

9 BIBLIOGRAPHY

9.1. Journal References 46

9.2. Book References 48

9.3. Web References 49

v
 CHAPTER - 1
INTRODUCTION

1.1 Company Profile

Company Profile: WAYTOWEB

At WAYTOWEB, we specialize in providing cutting-edge software development

solutions to drive your business forward. Our bespoke digital services are designed to
captivate your audience in today's fiercely competitive landscape.

WAYTOWEB is a premier software development firm in India, specializing in

exceptional web, mobile, and custom software applications. Our expert team delivers
top-notch development services, including iOS, Android, & cross-platform solutions, and
innovative web apps optimized for multi-user operation.

Since 2013, we have been dedicated to delivering high-quality services & ensuring client
satisfaction. Our creative and user-friendly applications can help your business grow
faster, and we stay up-to-date with the latest trends to offer innovative solutions that
meet your needs. Trust us to deliver your project on time and with the quality you
deserve.

We build custom software development to be ahead of one step in business. Get in touch
today to achieve your vision with our expert solutions.

Project Profile

1. Project overview
 The scheme aims to enable secure data sharing in cloud environments while
maintaining fine-grained access control and ensuring fairness and verifiability in
the delegation of decryption rights.

 The scheme addresses the need for secure and controlled data sharing in cloud
environments, offering fine-grained access control, delegation of decryption rights,
and mechanisms for ensuring fairness and verifiability in the process.

9
2 Project Goals
 Cloud Data Sharing: Enables secure sharing of sensitive data within organizations or between
different organizations in cloud environments.
 Collaborative Environments: Facilitates collaboration by allowing controlled access to shared data
based on predefined attributes.
 Secure Outsourcing: Provides a mechanism for securely outsourcing data storage and management
to cloud providers while maintaining control over access rights.
3 Project Scope
 Fine-grained Access Control: Access to data is controlled based on attributes, allowing for precise
control over who can decrypt it.
 Delegation of Decryption Rights: Proxy re-encryption enables the delegation of decryption rights
without compromising security.
 Fairness and Verifiability: The scheme includes mechanisms for ensuring fairness and verifiability
in the re-encryption process, enhancing trust and security in data sharing.

1
 CHAPTER - 2
SYSTEM ANALYSIS

2.1. Existing System

In that existing System , advanced encryption schemes can protect data confidentiality and enable fine-
grained data sharing for out sourced encrypted data, they cannot provide verifiability and fairness
 The user cannot ensure the validity of the re-encrypted ciphertext returned by the cloud server

Disadvantages
 The re-encryption doesn’t occur properly.
 The re-encryption computation’s complexity is linear with the size of the access policy, the
computation can be very expensive

2.2. Proposed System

 We present a formal definition of VF-ABPRE which considers the verifiability and fairness of
attribute-based encrypted data sharing in cloud computing.

 Then, we construct a concrete VF-ABPRE scheme and prove its confidentiality, verifiability and
fairness using the ABE-CR algorithm

 Finally, we conduct an implementation to evaluate the performance of our proposed scheme to

demonstrate its practicality and efficiency

Proposed System Advantages:

 The security and the performance is high

 Confidentiality of files while Upload/Download

1
 CHAPTER – 3

SYSTEM REQUIREMENTS

3.1. System Requirements:

Hardware Requirements:

• System : Intel i3.

• Hard Disk : 40 GB.

• Floppy Drive : 1.44 Mb.

• Monitor : 15 VGA Colour.

• Mouse : Logitech.

• Ram : 512 Mb.

Software Requirements:

• Operating system : Windows XP.

• Coding Language : JAVA

• Data Base : MYSQL

 IDE : Netbeans IDE

3.2. Software Description

Frontend Technology
 HTML (HyperText MarkUp language)
o HTML is the foundational language for creating webpage structure and content.
It defines the elements on a webpage, such as headings, paragraphs, images, and
links.

1
  CSS (Cascading Style Sheets)
o CSS is used to style and format HTML elements, allowing for design
customization such as colors, fonts, spacing, and layout. CSS can be used to
create responsive designs, ensuring the website looks good on various devices.
 Bootstrap
o Bootstrap is a popular CSS framework that provides pre-built components
and utilities to create responsive and mobile-friendly websites. It includes a
grid system, UI components (like buttons, modals, and forms), and other
useful features for rapid development

Backend Technologies

Software Environment
Java Technology

 Java technology is both a programming language and a platform.

The Java Programming Language

 The Java programming language is a high-level language that can be characterized by all of
the following buzzwords:

 Simple

 Architecture neutral

 Object oriented

 Portable

 Distributed

 High performance

 Interpreted

 Multithreaded

1
  Robust

 Dynamic

 Secure

 With most programming languages, you either compile or interpret a program so that you can run
it on your computer. The Java programming language is unusual in that a program is both
compiled and interpreted. With the compiler, first you translate a program into an intermediate
language called Java byte codes —the platform-independent codes interpreted by the interpreter
on the Java platform. The interpreter parses and runs each Java byte code instruction on the
computer. Compilation happens just once; interpretation occurs each time the program is executed.
The following figure illustrates how this works.


 You can think of Java byte codes as the machine code instructions for the Java Virtual Machine (Java
VM). Every Java interpreter, whether it’s a development tool or a Web browser that can run applets,
is an implementation of the Java VM.

 Java byte codes help make “write once, run anywhere” possible. You can compile your program into
byte codes on any platform that has a Java compiler. The byte codes can then be run on any
implementation of the Java VM.

 That means that as long as a computer has a Java VM, the same program written in the Java
programming language can run on Windows 2000, a Solaris workstation, or on an iMac.

1
The Java Platform

 A platform is the hardware or software environment in which program runs. We’ve already
mentioned some of the most popular platforms like Windows 2000, Linux, Solaris, and
MacOS. Most platforms can be described as a combination of the operating system and
hardware. The Java platform differs from most other platforms in that it’s a software-only
platform that runs on top of other hardware-based platforms.

The Java platform has two components:

 The Java Virtual Machine (Java VM)

 The Java Application Programming Interface (Java API)

You’ve already been introduced to the Java VM. It’s the base for the Java platform and is ported onto
various hardware-based platforms.

The Java API is a large collection of ready-made software components that provide many useful
capabilities, such as graphical user interface (GUI) widgets. The Java API is grouped into libraries of
related classes and interfaces; these libraries are known as packages. The next section, What Can Java
Technology Do? Highlights what functionality some of the packages in the Java API provide. The
following figure depicts a program that’s running on the Java platform. As the figure shows, the Java API
and the virtual machine insulate the program from the hardware.

1
 Native code is code that after you compile it, the compiled code runs on a specific
hardware platform. As a platform-independent environment, the Java platform can be a bit slower
than native code. However, smart compilers, well-tuned interpreters, and just-in-time byte code
compilers can bring performance close to that of native code without threatening portability.
What Can Java Technology Do?

The most common types of programs written in the Java programming language are applets and
applications. If you’ve surfed the Web, you’re probably already familiar with applets. An applet is
a program that adheres to certain conventions that allow it to run within a Java-enabled browser.

However, the Java programming language is not just for writing cute, entertaining applets for the
Web. The general-purpose, high-level Java programming language is also a powerful software
platform. Using the generous API, you can write many types of programs.

An application is a standalone program that runs directly on the Java platform. A special kind of
application known as a server serves and supports clients on a network. Examples of servers are
Web servers, proxy servers, mail servers, and print servers. Another specialized program is a
servlet. A servlet can almost be thought of as an applet that runs on the server side. Java Servlets
are a popular choice for building interactive web applications, replacing the use of CGI scripts.
Servlets are similar to applets in that they are runtime extensions of applications. Instead of
working in browsers, though, servlets run within Java Web servers, configuring or tailoring the
server. How does the API support all these kinds of programs? It does so with packages of
software components that provides a wide range of functionality. Every full implementation of the
Java platform gives you the following features:

 The essentials: Objects, strings, threads, numbers, input and output, data structures, system
properties, date and time, and so on.

 Applets: The set of conventions used by applets.

 Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram
Protocol) sockets, and IP (Internet Protocol) addresses.

 Internationalization: Help for writing programs that can be localized for users worldwide.
Programs can automatically adapt to specific locales and be displayed in the appropriate
language.

 Security: Both low level and high level, including electronic signatures, public and private
1
 key management, access control, and certificates.

 Software components: Known as JavaBeansTM, can plug into existing component

architectures.

 Object serialization: Allows lightweight persistence and communication via Remote

Method Invocation (RMI).

 Java Database Connectivity (JDBCTM): Provides uniform access to a wide range of

relational databases.

The Java platform also has APIs for 2D and 3D graphics, accessibility, servers, collaboration,
telephony, speech, animation, and more. The following figure depicts what is included in the Java
2 SDK.

How Will Java Technology Change My Life?

We can’t promise you fame, fortune, or even a job if you learn the Java programming
language. Still, it is likely to make your programs better and requires less effort than other
languages. We believe that Java technology will help you do the following:

 Get started quickly: Although the Java programming language is a powerful object-
oriented language, it’s easy to learn, especially for programmers already familiar with C or
C++.

 Write less code: Comparisons of program metrics (class counts, method counts, and so on)
suggest that a program written in the Java programming language can be four times smaller
1
 than the same program in C++.

 Write better code: The Java programming language encourages good coding practices,
and its garbage collection helps you avoid memory leaks. Its object orientation, its
JavaBeans component architecture, and its wide-ranging, easily extendible API let you
reuse other people’s tested code and introduce fewer bugs.

 Develop programs more quickly: Your development time may be as much as twice as
fast versus writing the same program in C++. Why? You write fewer lines of code and it is
a simpler programming language than C++.

 Avoid platform dependencies with 100% Pure Java: You can keep your program
portable by avoiding the use of libraries written in other languages. The 100% Pure
JavaTMProduct Certification Program has a repository of historical process manuals, white
papers, brochures, and similar materials online.

 Write once, run anywhere: Because 100% Pure Java programs are compiled into
machine-independent byte codes, they run consistently on any Java platform.

 Distribute software more easily: You can upgrade applets easily from a central server.
Applets take advantage of the feature of allowing new classes to be loaded “on the fly,”
without recompiling the entire program.

ODBC

Microsoft Open Database Connectivity (ODBC) is a standard programming interface for

application developers and database systems providers. Before ODBC became a de facto standard for
Windows programs to interface with database systems, programmers had to use proprietary languages for
each database they wanted to connect to. Now, ODBC has made the choice of the database system almost
irrelevant from a coding perspective, which is as it should be. Application developers have much more
important things to worry about than the syntax that is needed to port their program from one database to
another when business needs suddenly change.

Through the ODBC Administrator in Control Panel, you can specify the particular database that is
associated with a data source that an ODBC application program is written to use. Think of an ODBC data
source as a door with a name on it. Each door will lead you to a particular database. For example, the data
source named Sales Figures might be a SQL Server database, whereas the Accounts Payable data source
could refer to an Access database. The physical database referred to by a data source can reside anywhere
1
on the LAN.

The ODBC system files are not installed on your system by Windows 95. Rather, they are installed
when you setup a separate database application, such as SQL Server Client or Visual Basic 4.0. When the
ODBC icon is installed in Control Panel, it uses a file called ODBCINST.DLL. It is also possible to
administer your ODBC data sources through a stand-alone program called ODBCADM.EXE. There is a
16-bit and a 32-bit version of this program and each maintains a separate list of ODBC data sources.

From a programming perspective, the beauty of ODBC is that the application can be written to use
the same set of function calls to interface with any data source, regardless of the database vendor. The
source code of the application doesn’t change whether it talks to Oracle or SQL Server. We only mention
these two as an example. There are ODBC drivers available for several dozen popular database systems.
Even

Excel spreadsheets and plain text files can be turned into data sources. The operating system uses
the Registry information written by ODBC Administrator to determine which low-level ODBC drivers are
needed to talk to the data source (such as the interface to Oracle or SQL Server). The loading of the
ODBC drivers is transparent to the ODBC application program. In a client/server environment, the ODBC
API even handles many of the network issues for the application programmer.

The advantages of this scheme are so numerous that you are probably thinking there must be some
catch. The only disadvantage of ODBC is that it isn’t as efficient as talking directly to the native database
interface. ODBC has had many detractors make the charge that it is too slow. Microsoft has always
claimed that the critical factor in performance is the quality of the driver software that is used. In our
humble opinion, this is true. The availability of good ODBC drivers has improved a great deal recently.
And anyway, the criticism about performance is somewhat analogous to those who said that compilers
would never match the speed of pure assembly language. Maybe not, but the compiler (or ODBC) gives
you the opportunity to write cleaner programs, which means you finish sooner. Meanwhile, computers get
faster every year.

JDBC

In an effort to set an independent database standard API for Java; Sun Microsystems developed
Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access mechanism that

1
provides a consistent interface to a variety of RDBMSs. This consistent interface is achieved through the
use of “plug-in” database connectivity modules, or drivers. If a database vendor wishes to have JDBC
support, he or she must provide the driver for each platform that the database and Java run on.

To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC. As you discovered
earlier in this chapter, ODBC has widespread support on a variety of platforms. Basing JDBC on ODBC
will allow vendors to bring JDBC drivers to market much faster than developing a completely new
connectivity solution.

JDBC was announced in March of 1996. It was released for a 90 day public review that ended
June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon after.

The remainder of this section will cover enough information about JDBC for you to know what it is about
and how to use it effectively. This is by no means a complete overview of JDBC. That would fill an entire
book.

JDBC Goals

Few software packages are designed without goals in mind. JDBC is one that, because of its many
goals, drove the development of the API. These goals, in conjunction with early reviewer feedback, have
finalized the JDBC class library into a solid framework for building database applications in Java.

The goals that were set for JDBC are important. They will give you some insight as to why certain
classes and functionalities behave the way they do. The eight design goals for JDBC are as follows:

1. SQL Level API

The designers felt that their main goal was to define a SQL interface for Java. Although not the lowest
database interface level possible, it is at a low enough level for higher-level tools and APIs to be
created. Conversely, it is at a high enough level for application programmers to use it confidently.
Attaining this goal allows for future tool vendors to “generate” JDBC code and to hide many of
JDBC’s complexities from the end user.

2. SQL Conformance

SQL syntax varies as you move from database vendor to database vendor. In an effort to
support a wide variety of vendors, JDBC will allow any query

statement to be passed through it to the underlying database driver. This allows the connectivity

2
module to handle non-standard functionality in a manner that is suitable for its users.

3. JDBC must be implemental on top of common database interfaces

The JDBC SQL API must “sit” on top of other common SQL level APIs. This goal allows JDBC
to use existing ODBC level drivers by the use of a software interface. This interface would
translate JDBC calls to ODBC and vice versa.

4. Provide a Java interface that is consistent with the rest of the Java system

Because of Java’s acceptance in the user community thus far, the designers feel that they should
not stray from the current design of the core Java system.

5. Keep it simple

This goal probably appears in all software design goal listings. JDBC is no exception. Sun felt that
the design of JDBC should be very simple, allowing for only one method of completing a task per
mechanism. Allowing duplicate functionality only serves to confuse the users of the API.

6. Use strong, static typing wherever possible

Strong typing allows for more error checking to be done at compile time; also, less error appear at
runtime.

7. Keep the common cases simple

Because more often than not, the usual SQL calls used by the programmer are simple SELECT’s,
INSERT’s, DELETE’s and UPDATE’s, these queries should be simple to perform with JDBC.
However, more complex SQL statements should also be possible.

Finally, we decided to proceed the implementation using Java Networking.

And for dynamically updating the cache table we go for MS Access database.

Java ha two things: a programming language and a platform.

Java is a high-level programming language that is all of the following

2
 Simple Architecture-neutral

Object-oriented Portable

Distributed High-performance

Interpreted multithreaded

Robust Dynamic

Secure

Java is also unusual in that each Java program is both compiled and interpreted. With a
compile you translate a Java program into an intermediate language called Java byte codes the
platform-independent code instruction is passed and run on the computer.

Compilation happens just once; interpretation occurs each time the program is executed.
The figure illustrates how this works.

JavaProgram Interpreter

Compilers My Program

You can think of Java byte codes as the machine code instructions for the Java Virtual
Machine (Java VM). Every Java interpreter, whether it’s a Java development tool or a Web
browser that can run Java applets, is an implementation of the Java VM. The Java VM can also
be implemented in hardware.Java byte codes help make “write once, run anywhere” possible.
You can compile your Java program into byte codes on my platform that has a Java compiler.
The byte codes can then be run any implementation of the Java VM. For example, the same
Java program can run Windows NT, Solaris, and Macintosh.

2
 Networking

TCP/IP stack:

The TCP/IP stack is shorter than the OSI one.

TCP is a connection-oriented protocol; UDP (User Datagram Protocol) is a connectionless

protocol.

IP datagram’s

The IP layer provides a connectionless and unreliable delivery system. It considers each
datagram independently of the others. Any association between datagram must be supplied by the
higher layers. The IP layer supplies a checksum that includes its own header. The header includes
the source and destination addresses. The IP layer handles routing through an

Internet. It is also responsible for breaking up large datagram into smaller ones for transmission and
reassembling them at the other end.

2
 UDP

UDP is also connectionless and unreliable. What it adds to IP is a checksum for the contents of the
datagram and port numbers. These are used to give a client/server model - see later.

TCP

TCP supplies logic to give a reliable connection-oriented protocol above IP. It provides a virtual
circuit that two processes can use to communicate.

Internet addresses

In order to use a service, you must be able to find it. The Internet uses an address scheme for machines
so that they can be located. The address is a 32 bit integer which gives the IP address. This encodes a
network ID and more addressing. The network ID falls into various classes according to the size of the
network address.

Network address

Class A uses 8 bits for the network address with 24 bits left over for other addressing. Class B uses 16
bit network addressing. Class C uses 24 bit network addressing and class D uses all 32.

Subnet address

Internally, the UNIX network is divided into sub networks. Building 11 is currently on one
sub network and uses 10-bit addressing, allowing 1024 different hosts.

Host address

8 bits are finally used for host addresses within our subnet. This places a limit of 256
machines that can be on the subnet.

2
 Total address

The 32 bit address is usually written as 4 integers separated by dots.

Port addresses

A service exists on a host, and is identified by its port. This is a 16 bit number. To send a
message to a server, you send it to the port for that service of the host that it is running on. This
is not location transparency! Certain of these ports are "well known".

Sockets

A socket is a data structure maintained by the system to handle network connections. A socket is created
using the call socket. It returns an integer that is like a file descriptor. In fact, under Windows, this handle
can be used with Read File and Write File functions.

#include <sys/types.h>

#include <sys/socket.h>

intsocket(int family, int type, int protocol);

Here "family" will be AF_INET for IP communications, protocol will be zero, and type will depend
on whether TCP or UDP is used. Two processes wishing to communicate over a network create a
socket each. These are similar to two ends of a pipe - but the actual pipe does not yet exist.

JFree Chart

JFreeChart is a free 100% Java chart library that makes it easy for developers to display professional
quality charts in their applications. JFreeChart's extensive feature set includes:

2
 A consistent and well-documented API, supporting a wide range of chart types;

A flexible design that is easy to extend, and targets both server-side and client-side applications;

Support for many output types, including Swing components, image files (including PNG
and JPEG), and vector graphics file formats (including PDF, EPS and SVG);

JFreeChart is "open source" or, more specifically, free software. It is distributed under the
terms of the GNU Lesser General Public Licence (LGPL), which permits use in proprietary
applications.

1. Map Visualizations

Charts showing values that relate to geographical areas. Some examples include: (a)
population density in each state of the United States, (b) income per capita for each country in
Europe, (c) life expectancy in each country of the world. The tasks in this project include:

Sourcing freely redistributable vector outlines for the countries of the world,
states/provinces in particular countries (USA in particular, but also other areas);

Creating an appropriate dataset interface (plus default implementation), a rendered, and

integrating this with the existing XYPlot class in JFreeChart;

Testing, documenting, testing some more, documenting some more.

. Time Series Chart Interactivity

Implement a new (to JFreeChart) feature for interactive time series charts --- to display a separate
control that shows a small version of ALL the time series data, with a sliding "view" rectangle that allows
you to select the subset of the time series data to display in the main chart.
3. Dashboards

There is currently a lot of interest in dashboard displays. Create a flexible dashboard mechanism
that supports a subset of JFreeChart chart types (dials, pies, thermometers, bars, and lines/time series) that
can be delivered easily via both Java Web Start and an applet.
4. Property Editors

The property editor mechanism in JFreeChart only handles a small subset of the properties that can
be set for charts. Extend (or reimplement) this mechanism to provide greater end-user control over the

2
appearance of the charts.

J2ME (Java 2 Micro edition):-

Sun Microsystems defines J2ME as "a highly optimized Java run-time environment targeting a
wide range of consumer products, including pagers, cellular phones, screen-phones, digital set-top boxes
and car navigation systems." Announced in June 1999 at the JavaOne Developer Conference, J2ME
brings the cross-platform functionality of the Java language to smaller devices, allowing mobile wireless
devices to share applications. With J2ME, Sun has adapted the Java platform for consumer products that
incorporate or are based on small computing devices.

1. General J2ME architecture

J2ME uses configurations and profiles to customize the Java Runtime Environment (JRE). As a
complete JRE, J2ME is comprised of a configuration, which determines the JVM used, and a profile,
which defines the application by adding domain-specific classes. The configuration defines the basic run-
time environment as a set of core classes and a specific JVM that run on specific types of devices. We'll
discuss configurations in detail in the Theprofile defines the application; specifically, it adds domain-
specific classes to the J2ME configuration to define certain uses for devices. We'll cover profiles in depth
in the The following graphic depicts the relationship between the different virtual machines,
configurations, and profiles. It also draws a parallel with the J2SE API and its Java virtual machine. While
the J2SE virtual machine is generally referred to as a JVM, the J2ME virtual machines, KVM and CVM,
are subsets of JVM. Both KVM and CVM can be thought of as a kind of Java virtual machine -- it's just
that they are shrunken versions of the J2SE JVM and are specific to J2ME.

2
. Developing J2ME applications

Introduction In this section, we will go over some considerations you need to keep in mind when
developing applications for smaller devices. We'll take a look at the way the compiler is invoked when
using J2SE to compile J2ME applications. Finally, we'll explore packaging and deployment and the role
preverification plays in this process.

3.Design considerations for small devices

Developing applications for small devices requires you to keep certain strategies in mind during
the design phase. It is best to strategically design an application for a small device before you begin
coding. Correcting the code because you failed to consider all of the "gotchas" before developing the
application can be a painful process. Here are some design strategies to consider:

* Keep it simple. Remove unnecessary features, possibly making those features a separate, secondary
application.

Smaller is better. This consideration should be a "no brainer" for all developers. Smaller applications use
less memory on the device and require shorter installation times. Consider packaging your Java
applications as compressed Java Archive (jar) files.

* Minimize run-time memory use. To minimize the amount of memory used at run time, use scalar types
in place of object types. Also, do not depend on the garbage collector. You should manage the memory
efficiently yourself by setting object references to null when you are finished with them. Another way to
reduce run-time memory is to use lazy instantiation, only allocating objects on an as-needed basis. Other
ways of reducing overall and peak memory use on small devices are to release resources quickly, reuse
objects, and avoid exceptions.

4.Configurations overview

The configuration defines the basic run-time environment as a set of core classes and a specific
JVM that run on specific types of devices. Currently, two configurations exist for J2ME, though others
may be defined in the future:

* Connected Limited Device Configuration (CLDC)is used specifically with the KVM for 16-bit or 32-
bit devices with limited amounts of memory. This is the configuration (and the virtual machine) used for
developing small J2ME applications. Its size limitations make CLDC more interesting and challenging
(from a development point of view) than CDC. CLDC is also the configuration that we will use for

2
developing our drawing tool application. An example of a small wireless device running small
applications is a Palm hand-held computer.

* Connected Device Configuration (CDC)is used with the C virtual machine (CVM) and is used for 32-
bit architectures requiring more than 2 MB of memory. An example of such a device is a Net TV box.

5.J2ME profiles

What is a J2ME profile?

As we mentioned earlier in this tutorial, a profile defines the type of device supported. The Mobile
Information Device Profile (MIDP), for example, defines classes for cellular phones. It adds domain-
specific classes to the J2ME configuration to define uses for similar devices. Two profiles have been
defined for J2ME and are built upon CLDC: KJava and MIDP. Both KJava and MIDP are associated with
CLDC and smaller devices. Profiles are built on top of configurations. Because profiles are specific to the
size of the device (amount of memory) on which an application runs, certain profiles are associated with
certain configurations.

A skeleton profile upon which you can create your own profile, the Foundation Profile, is available for
CDC.

Profile 1: KJava

KJava is Sun's proprietary profile and contains the KJava API. The KJava profile is built on top of the
CLDC configuration. The KJava virtual machine, KVM, accepts the same byte codes and class file format
as the classic J2SE virtual machine. KJava contains a Sun-specific API that runs on the Palm OS. The
KJava API has a great deal in common with the J2SE Abstract Windowing Toolkit (AWT). However,

because it is not a standard J2ME package, its main package is com.sun.kjava. We'll learn more about the
KJava API later in this tutorial when we develop some sample applications.

Profile 2: MIDP

MIDP is geared toward mobile devices such as cellular phones and pagers. The MIDP, like KJava, is built
2
upon CLDC and provides a standard run-time environment that allows new applications and services to be
deployed dynamically on end user devices. MIDP is a common, industry-standard profile for mobile
devices that is not dependent on a specific vendor. It is a complete and supported foundation for mobile
application

development. MIDP contains the following packages, the first three of which are core CLDC packages,
plus three MIDP-specific packages.

* java.lang

* java.io

* java.util

* javax.microedition.io

* javax.microedition.lcdui

* javax. microedition.midlet

* javax.microedition.rms

3
 CHAPTER - 4

SYSTEM

DESIGN

4.1System Architecture

UML DIAGRAM:

USE CASE DIAGRAM:

3
CLASS DIAGRAM:

SEQUENCE DAIGRAM:

3
COLABORATION DAIAGRAM:

DEPLOYMENT DAIGRAM:

3
DATAFLOW DIAGRAM:

LEVEL 0:

LEVEL 1:

3
LEVEL 2:

LEVEL 3:

LEVEL 4:

3
LEVEL 5:

ER DIAGRAM:

Upload
files

Login Manage files

Registe Logout
r

DATA OWNER DATA USER

Logout
Registe
r
Downloa
Login
3 Request d files
Request
to TA
status
 CHAPTER-5
CHAPTER - 5
SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of components,
sub-assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of
ensuring that the
Software system meets its requirements and user expectations and does not fail in an unacceptable
manner. There are various types of test. Each test type addresses a specific testing requirement.

TYPES OF TESTS
3
Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and internal
code flow should be validated. It is the testing of individual software units of the application .it is done
after the completion of an individual unit before integration. This is a structural testing, that relies on
knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a
specific business process, application, and/or system configuration.
Unit tests ensure that each unique path of a business process performs accurately to the documented
specifications and contains clearly defined inputs and expected results.
Integration testing
Integration tests are designed to test integrated software components to determine if they actually
run as one program. Testing is event driven and is more concerned with the basic outcome of screens or
fields. Integration tests demonstrate that although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is correct and consistent. Integration testing is
specifically aimed at exposing the problems that arise from the combination of components.
Functional test
Functional tests provide systematic demonstrations that functions tested are available as specified by
the business and technical requirements, system documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions, or
special test cases. In addition, systematic coverage pertaining to identify Business process flows; data
fields, predefined processes, and successive processes must be considered for testing. Before functional
testing is complete, additional tests are identified and the effective value of current tests is determined.

System Test
System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the configuration
oriented system integration test. System testing is based on process descriptions and flows, emphasizing
pre-driven process links and integration points.

3
White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test
areas that cannot be reached from a black box level.

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner workings, structure or
language of the module being tested. Black box tests, as most other kinds of tests, must be written from a
definitive source document, such as specification or requirements document, such as specification or
requirements document. It is a testing in which the software under test is treated, as a black box. you
cannot “see” into it. The test provides inputs and responds to outputs without considering how the
software works.
5.1 Unit Testing:
Unit testing is usually conducted as part of a combined code and unit test phase of the software
lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.
Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail. Test
objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

5.2 Integration Testing

Software integration testing is the incremental integration testing of two or more integrated
software components on a single platform to produce failures caused by interface defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level – interact
without error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
5.3 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant participation by
the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
3
.

4
 CHAPTER - 6
SYSTEM IMPLEMENTATION

6.1. System Description

ALGORITHMS

ABE
Attribute-based encryption (ABE) can be used for log encryption. Instead of encrypting each part
of a log with the keys of all recipients, it is possible to encrypt the log only with attributes which match
recipients' attributes.

Cipher Text
Cipher text is also known as encrypted or encoded information because it contains a form of the
original plaintext that is unreadable by a human or computer without the proper cipher to decrypt it.
Decryption, the inverse of encryption, is the process of turning cipher text into readable plaintext.

4.3.2MODULE DESCRIPTION

In this project have four modules:

 Data Owner

 Shared Users

 Cloud

 Authority

4
DATAOWNER

 Register the account with the basic information

 After authorize user can login the account with correct username and password

 Upload the file with the encryption format using the ABE –CR algorithm

 View user request and Make a request for re-encryption

 View the status and Re-Encrypted the key

 Logout

USER

 Register the account with the basic information

 After authorize user can login the account with correct username and password

 Profile

 Send Download request

 Download file

 Logout

CLOUDSERVER

 Login the account with the correct username and password

 View all uploaded files

 View Re-Encryption request and Send the Responses

 View all downloaded files

 Graph

 Logout

4
AUTHORITY

 Authority can login the account with the correct Credentials

 View users and owners authorize them

 View user Download request and Send the Key

 Logout

4
 CHAPTER -
7
APPENDICES

7.1. Screenshots & Source code

4
4
4
4
4
4
5
5
 CHAPTER - 8
CONCLUSION
8.1. Conclusion

This project introduces the verifiability and fairness security requirements for attribute-based data sharing
in clouds and put forward a notion of verifiable and fair ciphertext policy attribute-based proxy re-
encryption (VF-CP-ABPRE). The scheme provides the ability for a shared user to verify the validity of
the re-encrypted ciphertext. Moreover, a shared user cannot make a malicious accusation to the cloud
provider if the cloud has indeed returned a correct re-encrypted ciphertext.We also have proven our VF-
CP-ABPRE scheme’s semantic security, verifiability and fairness in our security model.

8.2. Future Enhancement

For our future work, we will try to implement these methods using the different algorithms in the real
Cloud like AWS, Azure etc.

5
 CHAPTER - 9
BIBLIOGRAPHY

REFERENCE
[1] K. Ren, C. Wang, and Q. Wang, “Security challenges for the public cloud,” IEEE Internet Computing,
vol. 16, no. 1, pp. 69–73, 2012.
[2] A. Sahai and B. Waters, “Fuzzy identity-based encryption,” in International Conference on Theory
and Applications of Cryptographic Techniques, 2005, pp. 457–473.
[3] J. Lai, R. H. Deng, C. Guan, and J. Weng, “Attribute-based encryption with verifiable outsourced
decryption,” IEEE Transactions on information forensics and security, vol. 8, no. 8, pp. 1343–1354, 2013.
[4] H. Ma, R. Zhang, Z. Wan, Y. Lu, and S. Lin, “Verifiable and exculpable outsourced attribute-based
encryption for access control in cloud computing,” IEEE transactions on dependable and secure
computing, vol. 14, no. 6, pp. 679–692, 2015.
[5] J. Bethencourt, A. Sahai, and B. Waters, “Ciphertext-policy attributebased encryption,” in IEEE
Symposium on Security and Privacy, 2007, pp. 321–334.
[6] V. Goyal, O. Pandey, A. Sahai, and B. Waters, “Attribute-based encryption for fine-grained access
control of encrypted data,” in ACM Conference on Computer and Communications Security, 2006, pp.
89–98.
[7] K. Emura, A. Miyaji, A. Nomura, K. Omote, and M. Soshi, “A ciphertext-policy attribute-based
encryption scheme with constant ciphertext length,” in International Conference on Information Security
Practice and Experience. Springer, 2009, pp. 13–23.
[8] S. Hohenberger and B. Waters, “Attribute-based encryption with fast decryption,” in International
Workshop on Public Key Cryptography. Springer, 2013, pp. 162–179.
9] N. Attrapadung, B. Libert, and E. De Panafieu, “Expressive key-policy attribute-based encryption with
constant-size ciphertexts,” in International Workshop on Public Key Cryptography. Springer, 2011,
pp.90–108
[10] J. Herranz, F. Laguillaumie, and C. Rafols, “Constant size ciphertexts ` in threshold attribute-based
encryption,” in International Workshop on Public Key Cryptography. Springer, 2010, pp. 19–34.

5
9.1. Web References
• GOOGLE

• CHAT GPT

• java.org

• Solo learn