1.

INTRODUCTION
1.1 OVERVIEW:

Cloud computing is the use of computing resources (hardware and software)

that are delivered as a service over a network (typically the Internet). The name comes
from the common use of a cloud-shaped symbol as an abstraction for the complex
infrastructure it contains in system diagrams. Cloud computing entrusts remote
services with a user's data, software and computation. Cloud computing consists of
hardware and software resources made available on the Internet as managed third-
party services. These services typically provide access to advanced software
applications and high-end networks of server computers.

1.1 Structure of cloud computing

1
CLOUD COMPUTING WORKS:

The goal of cloud computing is to apply traditional supercomputing, or high-

performance computing power, normally used by military and research facilities, to
perform tens of trillions of computations per second, in consumer-oriented
applications such as financial portfolios, to deliver personalized information, to
provide data storage or to power large, immersive computer games.
The cloud computing uses networks of large groups of servers typically
running low-cost consumer PC technology with specialized connections to spread
data-processing chores across them. This shared IT infrastructure contains large pools
of systems that are linked together. Often, virtualization techniques are used to
maximize the power of cloud computing.

CHARACTERSTICS OF SERVICE MODELS:

The salient characteristics of cloud computing based on the definitions

provided by the National Institute of Standards and Terminology (NIST) are outlined
below:

 On-demand self-service: A consumer can unilaterally provision computing

capabilities, such as server time and network storage, as needed automatically
without requiring human interaction with each service’s provider.
 Broad network access: Capabilities are available over the network and
accessed through standard mechanisms that promote use by heterogeneous
thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
 Resource pooling: The provider’s computing resources are pooled to serve
multiple consumers using a multi-tenant model, with different physical and
virtual resources dynamically assigned and reassigned according to consumer
demand. There is a sense of location-independence in that the customer
generally has no control or knowledge over the exact location of the provided
resources but may be able to specify location at a higher level of abstraction
(e.g., country, state, or data center). Examples of resources include storage,
processing, memory, network bandwidth, and virtual machines.
 Rapid elasticity: Capabilities can be rapidly and elastically provisioned, in
some cases automatically, to quickly scale out and rapidly released to quickly
2
 scale in. To the consumer, the capabilities available for provisioning often
appear to be unlimited and can be purchased in any quantity at any time.
 Measured service: Cloud systems automatically control and optimize
resource use by leveraging a metering capability at some level of abstraction
appropriate to the type of service (e.g., storage, processing, bandwidth, and
active useraccounts).

Cloud Computing comprises three different service models, namely

Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-
Service (SaaS). The three service models or layer are completed by an end user layer
that encapsulates the end user perspective on cloud services. The model is shown in
figure below. If a cloud user accesses services on the infrastructure layer, for instance,
she can run her own applications on the resources of a cloud infrastructure and remain
responsible for the support, maintenance, and security of these applications herself. If
she accesses a service on the application layer, these tasks are normally taken care of
by the cloud service provider.

1.2 Structure of service models

3
 BENEFITS OF CLOUD COMPUTING:

1. Achieve economies of scale – increase volume output or productivity with

fewer people. Your cost per unit, project or product plummets.
2. Reduce spending on technology infrastructure. Maintain easy access to
your information with minimal upfront spending. Pay as you go (weekly,
quarterly or yearly), based on demand.
3. Globalize your workforce on the cheap. People worldwide can access the
cloud, provided they have an Internet connection.
4. Streamline processes. Get more work done in less time with less people.
5. Reduce capital costs. There’s no need to spend big money on hardware,
software or licensing fees.
6. Improve accessibility. You have access anytime, anywhere, making your life
so much easier!
7. Monitor projects more effectively. Stay within budget and ahead of
completion cycle times.
8. Less personnel training is needed. It takes fewer people to do more work on
a cloud, with a minimal learning curve on hardware and software issues.
9. Minimize licensing new software. Stretch and grow without the need to buy
expensive software licenses or programs.
10. Improve flexibility. You can change direction without serious “people” or
“financial” issues at stake.

Advantages:

1. Price: Pay for only the resources used.

2. Security: Cloud instances are isolated in the network from other instances for
improved security.
3. Performance: Instances can be added instantly for improved performance.
Clients have access to the total resources of the Cloud’s core hardware.
4. Scalability: Auto-deploy cloud instances when needed.

4
SYSTEM ANALYSIS

1.3 EXISTING SYSTEM:

 Existing work on access control in cloud are centralized in nature. Except

and, all other schemes use ABE. The scheme in uses a symmetric key
approach and does not support authentication. The schemes do not support
authentication as well.
 It provides privacy preserving authenticated access control in cloud.
However, the authors take a centralized approach where a single key
distribution center (KDC) distributes secret keys and attributes to all users.

DISADVANTAGES OF EXISTING SYSTEM:

 The scheme in uses asymmetric key approach and does not support
authentication.
 Difficult to maintain because of the large number of users that are
supported in a cloud environment.

5
1.4 PROPOSED SYSTEM:

 We propose a new decentralized access control scheme for secure data

storage in clouds that supports anonymous authentication.
 In the proposed scheme, the cloud verifies the authenticity of the series
without knowing the user’s identity before storing data.
 Our scheme also has the added feature of access control in which only
valid users are able to decrypt the stored information.
 The scheme prevents replay attacks and supports creation, modification,
and reading data stored in the cloud.

ADVANTAGES OF PROPOSED SYSTEM:

 Distributed access control of data stored in cloud so that only authorized

users with valid attributes can access them.
 Authentication of users who store and modify their data on the cloud.

6
1.5 LITERATURE SURVEY

1) “Privacy Preserving Access Control with Authentication for Securing Data in

Clouds,”

AUTHORS: S. Ruj, M. Stojmenovic, and A. Nayak

In this paper, propose a new privacy preserving authenticated access control

scheme for securing data in clouds. In the proposed scheme, the cloud verifies the
authenticity of the user without knowing the user's identity before storing information.
Our scheme also has the added feature of access control in which only valid users are
able to decrypt the stored information. The scheme prevents replay attacks and
supports creation, modification, and reading data stored in the cloud. Moreover, our
authentication and access control scheme is decentralized and robust, unlike other
access control schemes designed for clouds which are centralized. The
communication, computation, and storage overheads are comparable to centralized
approaches.

2. “Toward Secure and Dependable Storage Services in Cloud Computing”

AUTHORS: C. Wang, Q. Wang, K. Ren, N. Cao, and W. Lou

Cloud storage enables users to remotely store their data and enjoy the on-
demand high quality cloud applications without the burden of local hardware and
software management. Though the benefits are clear, such a service is also
relinquishing users' physical possession of their outsourced data, which inevitably
poses new security risks toward the correctness of the data in cloud. In order to
address this new problem and further achieve a secure and dependable cloud storage
service, we propose in this paper a flexible distributed storage integrity auditing
mechanism, utilizing the homomorphic token and distributed erasure-coded data. The
proposed design allows users to audit the cloud storage with very lightweight
communication and computation cost. The auditing result not only ensures strong
cloud storage correctness guarantee, but also simultaneously achieves fast data error
localization, i.e., the identification of misbehaving server. Considering the cloud data
are dynamic in nature, the proposed design further supports secure and efficient

7
dynamic operations on outsourced data, including block modification, deletion, and
append. Analysis shows the proposed scheme is highly efficient and resilient against
Byzantine failure, malicious data modification attack, and even server colluding
attacks.

3. “Cryptographic Cloud Storage,”

AUTHORS: S. Kamara and K. Lauter,

It consider the problem of building a secure cloud storage service on top of a

public cloud infrastructure where the service provider is not completely trusted by the
customer. We describe, at a high level, several architectures that combine recent and
non-standard cryptographic primitives in order to achieve our goal. We survey the
benefits such an architecture would provide to both customers and service providers
and give an overview of recent advances in cryptography motivated specifically by
cloud storage.

4. “Identity-Based Authentication for Cloud Computing,”

AUTHORS: H. Li, Y. Dai, L. Tian, and H. Yang

Cloud computing is a recently developed new technology for complex systems

with massive-scale services sharing among numerous users. Therefore, authentication
of both users and services is a significant issue for the trust and security of the cloud
computing. SSL Authentication Protocol (SAP), once applied in cloud computing,
will become so complicated that users will undergo a heavily loaded point both in
computation and communication. This paper, based on the identity-based hierarchical
model for cloud computing (IBHMCC) and its corresponding encryption and
signature schemes, presented a new identity-based authentication protocol for cloud
computing and services. Through simulation testing, it is shown that the
authentication protocol is more lightweight and efficient than SAP, specially the more
lightweight user side. Such merit of our model with great scalability is very suited to
the massive-scale cloud.

8
5.“Improving Privacy and Security in Multi-Authority Attribute-Based
Encryption,”

AUTHORS: M. Chase and S.S.M. Chow

Attribute based encryption (ABE) [13] determines decryption ability based on

a user's attributes. In a multi-authority ABE scheme, multiple attribute-authorities
monitor different sets of attributes and issue corresponding decryption keys to users,
and encryptors can require that a user obtain keys for appropriate attributes from each
authority before decrypting a message. Chase [5] gave a multi-authority ABE scheme
using the concepts of a trusted central authority (CA) and global identifiers (GID).
However, the CA in that construction has the power to decrypt every ciphertext,
which seems somehow contradictory to the original goal of distributing control over
many potentially untrusted authorities. Moreover, in that construction, the use of a
consistent GID allowed the authorities to combine their information to build a full
profile with all of a user's attributes, which unnecessarily compromises the privacy of
the user. In this paper, we propose a solution which removes the trusted central
authority, and protects the users' privacy by preventing the authorities from pooling
their information on particular users, thus making ABE more usable in practice.

9
 THEME OF THE PROJECT

2.1 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
 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.

10
 3.1 Program structure

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.
The Java Platform
A platform is the hardware or software environment in which a 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.

11
 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.

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.

12
 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 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.

4. default JRE
13
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 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 JavaTM Product 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

14
 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 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
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
15
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 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

16
 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 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.
5. 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.

6. 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.

7. 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.
17
 8. 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.
Java ha two things: a programming language and a platform. Java is a
high-l evel programming language that is all of the following

Simple Architecture-neutral
Object-oriented Portable
Distributed High-performance
Interpreted multithreaded
Robust Dynamic

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.

Java Program Interpreter

Compilers My Program

18
 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.
NETWORK:
TCP/IP stack
The TCP/IP stack is shorter than the OSI one:

4.1.1 TCP/IP stack

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

19
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.
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.
Total address

20
 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>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol will bezero,
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:
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);

21
 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.
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.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.
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.
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 appearance of the charts.
What is a Java Web Application?
A Java web application generates interactive web pages containing various
types of markup language (HTML, XML, and so on) and dynamic content. It is
typically comprised of web components such as JavaServer Pages (JSP), servlets and
JavaBeans to modify and temporarily store data, interact with databases and web
services, and render content in response to client requests.
Because many of the tasks involved in web application development can be
repetitive or require a surplus of boilerplate code, web frameworks can be applied to
alleviate the overhead associated with common activities. For example, many

22
frameworks, such as JavaServer Faces, provide libraries for templating pages and
session management, and often promote code reuse.
What is Java EE?
Java EE (Enterprise Edition) is a widely used platform containing a set of
coordinated technologies that significantly reduce the cost and complexity of
developing, deploying, and managing multi-tier, server-centric applications. Java EE
builds upon the Java SE platform and provides a set of APIs (application
programming interfaces) for developing and running portable, robust, scalable,
reliable and secure server-side applications.
Some of the fundamental components of Java EE include:
 Enterprise JavaBeans (EJB): a managed, server-side component architecture
used to encapsulate the business logic of an application. EJB technology
enables rapid and simplified development of distributed, transactional, secure
and portable applications based on Java technology.
 Java Persistence API (JPA): a framework that allows developers to manage
data using object-relational mapping (ORM) in applications built on the Java
Platform.
JavaScript and Ajax Development
JavaScript is an object-oriented scripting language primarily used in client-
side interfaces for web applications. Ajax (Asynchronous JavaScript and XML) is a
Web 2.0 technique that allows changes to occur in a web page without the need to
perform a page refresh. JavaScript toolkits can be leveraged to implement Ajax-
enabled components and functionality in web pages.
Web Server and Client
Web Server is a software that can process the client request and send the
response back to the client. For example, Apache is one of the most widely used web
server. Web Server runs on some physical machine and listens to client request on
specific port.
A web client is a software that helps in communicating with the server. Some of the
most widely used web clients are Firefox, Google Chrome, Safari etc. When we
request something from server (through URL), web client takes care of creating a
request and sending it to server and then parsing the server response and present it to
the user.

23
HTML and HTTP
Web Server and Web Client are two separate softwares, so there should be
some common language for communication. HTML is the common language between
server and client and stands for HyperText Markup Language.
Web server and client needs a common communication protocol, HTTP (HyperText
Transfer Protocol) is the communication protocol between server and client. HTTP
runs on top of TCP/IP communication protocol.
Some of the important parts of HTTP Request are:
 HTTP Method – action to be performed, usually GET, POST, PUT etc.
 URL – Page to access
 Form Parameters – similar to arguments in a java method, for example
user,password details from login page.
Sample HTTP Request:
1GET /FirstServletProject/jsps/hello.jsp HTTP/1.1
2Host: localhost:8080
3Cache-Control: no-cache
Some of the important parts of HTTP Response are:
 Status Code – an integer to indicate whether the request was success or not.
Some of the well known status codes are 200 for success, 404 for Not Found
and 403 for Access Forbidden.
 Content Type – text, html, image, pdf etc. Also known as MIME type
 Content – actual data that is rendered by client and shown to user.

MIME Type or Content Type: If you see above sample HTTP response header, it
contains tag “Content-Type”. It’s also called MIME type and server sends it to client
to let them know the kind of data it’s sending. It helps client in rendering the data for
user. Some of the mostly used mime types are text/html, text/xml, application/xml etc.
Understanding URL
URL is acronym of Universal Resource Locator and it’s used to locate the
server and resource. Every resource on the web has it’s own unique address. Let’s see
parts of URL with an example.
http://localhost:8080/FirstServletProject/jsps/hello.jsp
http:// – This is the first part of URL and provides the communication protocol to be
used in server-client communication.
24
localhost – The unique address of the server, most of the times it’s the hostname of
the server that maps to unique IP address. Sometimes multiple hostnames point to
same IP addresses and web server virtual host takes care of sending request to the
particular server instance.
8080 – This is the port on which server is listening, it’s optional and if we don’t
provide it in URL then request goes to the default port of the protocol. Port numbers 0
to 1023 are reserved ports for well known services, for example 80 for HTTP, 443 for
HTTPS, 21 for FTP etc.
FirstServletProject/jsps/hello.jsp – Resource requested from server. It can be static
html, pdf, JSP, servlets, PHP etc.
Why we need Servlet and JSPs?
Web servers are good for static contents HTML pages but they don’t know
how to generate dynamic content or how to save data into databases, so we need
another tool that we can use to generate dynamic content. There are several
programming languages for dynamic content like PHP, Python, Ruby on Rails, Java
Servlets and JSPs.
Java Servlet and JSPs are server side technologies to extend the capability of
web servers by providing support for dynamic response and data persistence.
Web Container
Tomcat is a web container, when a request is made from Client to web server,
it passes the request to web container and it’s web container job to find the correct
resource to handle the request (servlet or JSP) and then use the response from the
resource to generate the response and provide it to web server. Then web server sends
the response back to the client.
When web container gets the request and if it’s for servlet then container
creates two Objects HTTPServletRequest and HTTPServletResponse. Then it finds
the correct servlet based on the URL and creates a thread for the request. Then it
invokes the servlet service() method and based on the HTTP method service() method
invokes doGet() or doPost() methods.
Servlet methods generate the dynamic page and write it to response. Once
servlet thread is complete, container converts the response to HTTP response and
send it back to client.
Some of the important work done by web container are:

25
  Communication Support – Container provides easy way of communication
between web server and the servlets and JSPs. Because of container, we don’t
need to build a server socket to listen for any request from web server, parse
the request and generate response. All these important and complex tasks are
done by container and all we need to focus is on our business logic for our
applications.
 Lifecycle and Resource Management – Container takes care of managing
the life cycle of servlet. Container takes care of loading the servlets into
memory, initializing servlets, invoking servlet methods and destroying them.
Container also provides utility like JNDI for resource pooling and
management.
 Multithreading Support – Container creates new thread for every request to
the servlet and when it’s processed the thread dies. So servlets are not
initialized for each request and saves time and memory.
 JSP Support – JSPs doesn’t look like normal java classes and web container
provides support for JSP. Every JSP in the application is compiled by
container and converted to Servlet and then container manages them like other
servlets.
 Miscellaneous Task – Web container manages the resource pool, does
memory optimizations, run garbage collector, provides security
configurations, support for multiple applications, hot deployment and several
other tasks behind the scene that makes our life easier.
Web Application Directory Structure
Java Web Applications are packaged as Web Archive (WAR) and it has a
defined structure. You can export above dynamic web project as WAR file and unzip
it to check the hierarchy. It will be something like below image.

26
Deployment Descriptor
web.xml file is the deployment descriptor of the web application and contains
mapping for servlets (prior to 3.0), welcome pages, security configurations, session
timeout settings etc.
Thats all for the java web application startup tutorial, we will explore Servlets
and JSPs more in future posts.
MySQL:
MySQL, the most popular Open Source SQL database management system, is
developed, distributed, and supported by Oracle Corporation.
The MySQL Web site (http://www.mysql.com/) provides the latest information about
MySQL software.

 MySQL is a database management system.

A database is a structured collection of data. It may be anything from a simple
shopping list to a picture gallery or the vast amounts of information in a corporate
network. To add, access, and process data stored in a computer database, you need
a database management system such as MySQL Server. Since computers are very

27
 good at handling large amounts of data, database management systems play a
central role in computing, as standalone utilities, or as parts of other applications.
MySQL databases are relational.
A relational database stores data in separate tables rather than putting all the
data in one big storeroom. The database structures are organized into physical files
optimized for speed. The logical model, with objects such as databases, tables, views,
rows, and columns, offers a flexible programming environment.
You set up rules governing the relationships between different data fields,
such as one-to-one, one-to-many, unique, required or optional, and “pointers”
between different tables. The database enforces these rules, so that with a well-
designed database, your application never sees inconsistent, duplicate, orphan, out-of-
date, or missing data.
The SQL part of “MySQL” stands for “Structured Query Language”. SQL is
the most common standardized language used to access databases.
Depending on your programming environment, you might enter SQL directly
(for example, to generate reports), embed SQL statements into code written in another
language, or use a language-specific API that hides the SQL syntax.
SQL is defined by the ANSI/ISO SQL Standard. The SQL standard has been
evolving since 1986 and several versions exist. In this manual, “SQL-92” refers to the
standard released in 1992, “SQL:1999” refers to the standard released in 1999, and
“SQL:2003” refers to the current version of the standard. We use the phrase “the SQL
standard” to mean the current version of the SQL Standard at any time.
MySQL software is Open Source.
Open Source means that it is possible for anyone to use and modify the
software. Anybody can download the MySQL software from the Internet and use it
without paying anything. If you wish, you may study the source code and change it to
suit your needs. The MySQL software uses the GPL (GNU General Public License),
http://www.fsf.org/licenses/, to define what you may and may not do with the
software in different situations.
If you feel uncomfortable with the GPL or need to embed MySQL code into a
commercial application, you can buy a commercially licensed version from us. See
the MySQL Licensing Overview for more information
(http://www.mysql.com/company/legal/licensing/).
The MySQL Database Server is very fast, reliable, scalable, and easy to use.
28
 If that is what you are looking for, you should give it a try. MySQL Server can
run comfortably on a desktop or laptop, alongside your other applications, web
servers, and so on, requiring little or no attention.
If you dedicate an entire machine to MySQL, you can adjust the settings to
take advantage of all the memory, CPU power, and I/O capacity available. MySQL
can also scale up to clusters of machines, networked together.
You can find a performance comparison of MySQL Server with other
database managers on our benchmark page.
MySQL Server was originally developed to handle large databases much
faster than existing solutions and has been successfully used in highly demanding
production environments for several years. Although under constant development,
MySQL Server today offers a rich and useful set of functions.
Its connectivity, speed, and security make MySQL Server highly suited for
accessing databases on the Internet.

MySQL Server works in client/server or embedded systems.

The MySQL Database Software is a client/server system that consists of a
multi-threaded SQL server that supports different backends, several different client
programs and libraries, administrative tools, and a wide range of application
programming interfaces (APIs).
We also provide MySQL Server as an embedded multi-threaded library that
you can link into your application to get a smaller, faster, easier-to-manage standalone
product.
A large amount of contributed MySQL software is available.

29
 SYSTEM REQUIREMENTS:

2.1.1 HARDWARE REQUIREMENTS:

 System : Pentium IV 2.4 GHz.

 Hard Disk : 40 GB.
 Floppy Drive : 1.44 Mb.
 Monitor : 15 VGA Colour.
 Mouse : Logitech.
 Ram : 512 Mb.

2.1.2 SOFTWARE REQUIREMENTS:

 Operating system : Windows XP/7.

 Coding Language : JAVA/J2EE
 IDE : Netbeans 7.4
 Database : MYSQL
30
2.2 SYSTEM DESIGN:

SYSTEM ARCHITECTURE:

31
 The scheme prevents replay attacks and supports creation, modification, and
reading data stored in the cloud. We also address user revocation. Moreover, our
authentication and access control scheme is decentralized and robust, unlike other
access control schemes designed for clouds which are centralized.

The communication, computation, and storage overheads are comparable to

centralized approaches. In this the cloud verifies the authenticity of the series without
knowing the user’s identity before storing data.

2.2.1 DATA FLOW DIAGRAM:

The DFD is also called as bubble chart. It is a simple graphical formalism that
can be used to represent a system in terms of input data to the system, various
processing carried out on this data, and the output data is generated by this system.

32
 Login

False

Condition
True

Admin
Trustee User Login

Attrribute Analysis View File

Creator Reader Writer

Secret Key Key Received Request to KDC Response from KDC

Owner File Upload File read Modify Owner File

User Activation User details Name

Cloud Storage

END

The data flow diagram (DFD) is one of the most important modeling tools. It
is used to model the system components. These components are the system process,
the data used by the process, an external entity that interacts with the system and the
information flows in the system.
DFD shows how the information moves through the system and how it is
modified by a series of transformations. It is a graphical technique that depicts

33
information flow and the transformations that are applied as data moves from input to
output.
DFD is also known as bubble chart. A DFD may be used to represent a system
at any level of abstraction. DFD may be partitioned into levels that represent
increasing information flow and functional detail.
UML DIAGRAMS

UML stands for Unified Modeling Language. UML is a standardized general-

purpose modeling language in the field of object-oriented software engineering. The
standard is managed, and was created by, the Object Management Group.
The goal is for UML to become a common language for creating models of
object oriented computer software. In its current form UML is comprised of two
major components: a Meta-model and a notation. In the future, some form of method
or process may also be added to; or associated with, UML.
The Unified Modeling Language is a standard language for specifying,
Visualization, Constructing and documenting the artifacts of software system, as well
as for business modeling and other non-software systems.
The UML represents a collection of best engineering practices that have
proven successful in the modeling of large and complex systems.
The UML is a very important part of developing objects oriented software
and the software development process. The UML uses mostly graphical notations to
express the design of software projects.

USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of
actors, their goals (represented as use cases), and any dependencies between those use
cases. The main purpose of a use case diagram is to show what system functions are

34
performed for which actor. Roles of the actors in the system can be depicted.

Secret Key

Attribute Validation

User Activation

Trustee Trust Key Generation USER

Creator

KDC
Reader

Writer

CLASS DIAGRAM:

In software engineering, a class diagram in the Unified Modeling Language

(UML) is a type of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes, operations (or methods), and the
relationships among the classes. It explains which class contains information.

35
 KDC USER
Random_Value; File_ID;
User_ID;

Creator()
KeyGeneration() Reader()
Response() Modify()

TRUSTEE
USER_ID;

AttributeValidation()
KeyFormation()

SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language (UML) is a kind of

interaction diagram that shows how processes operate with one another and in what
order. It is a construct of a Message Sequence Chart. Sequence diagrams are
sometimes called event diagrams, event scenarios, and timing diagrams.

36
 KDC Trustee User

Key Generation
Attrribute Vaidation
Creator
Key Formation

Response
Reader

Writer

ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the business

37
and operational step-by-step workflows of components in a system. An activity
diagram shows the overall flow of control.

Login

False

Condition
True

Admin
Trustee User Login

Attrribute Analysis View File

Creator Reader Writer

Secret Key Key Received Request to KDC Response from KDC

Owner File Upload File read Modify Owner File

User Activation User details Name

Cloud Storage

2.3 SYSTEM STUDY

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is
put forth with a very general plan for the project and some cost estimates. During

38
system analysis the feasibility study of the proposed system is to be carried out. This
is to ensure that the proposed system is not a burden to the company. For feasibility
analysis, some understanding of the major requirements for the system is essential.

ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the system will
have on the organization. The amount of fund that the company can pour into the
research and development of the system is limited. The expenditures must be justified.
Thus the developed system as well within the budget and this was achieved because
most of the technologies used are freely available.

TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on
the available technical resources. This will lead to high demands on the available
technical resources.

SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the
user. This includes the process of training the user to use the system efficiently. The
user must not feel threatened by the system, instead must accept it as a necessity.

2.4 IMPLEMENTATION

MODULES:

 System Initialization.

39
  User Registration.
 KDC setup.
 Attribute generation.
 Sign.
 Verify.

MODULES DESCRIPTION:

System Initialization:
Select a prime q, and groups G1 and G2, which are of order q. We define the
mapping ˆe : G1 ×G1 → G2. Let g1, g2 be generators of G1 and hj be generators of
G2, for j ∈ [tmax], for arbitrary tmax. Let H be a hash function. Let A0 = ha0 0 ,
where a0 ∈ Z∗ q is chosen at random.
(TSig,TV er) mean TSig is the private key with which a message is signed and
TV er is the public key used for verification. The secret key for the trustee is TSK =
(a0, TSig) and public key is TPK = (G1,G2,H, g1,A0, h0, h1, . . . , htmax, g2, TV er).
User Registration:
For a user with identity Uu the KDC draws at random Kbase ∈ G. Let K0 =
K1/a0 base . The following token γ is output γ = (u,Kbase,K0, ρ), where ρ is
signature on u||Kbase using the signing key TSig.
KDC setup:
We emphasize that clouds should take a decentralized approach while
distributing secret keys and attributes to users. It is also quite natural for clouds to
have many KDCs in different locations in the world. The architecture is decentralized,
meaning that there can be several KDCs for key management.
The token verification algorithm verifies the signature contained in γ using the
signature verification key TV er in TPK. This algorithm extracts Kbase from γ using
(a, b) from ASK[i] and computes Kx = K1/(a+bx) base , x ∈ J[i, u]. The key Kx can
be checked for consistency using algorithm ABS.KeyCheck(TPK,APK[i], γ,Kx),
which checks ˆe(Kx,AijBx ij) = ˆe(Kbase, hj), for all x ∈ J[i, u] and j ∈ [tmax].
Sign:
The access policy decides who can access the data stored in the cloud. The
creator decides on a claim policy Y, to prove her authenticity and signs the message
under this claim.

40
 The ciphertext C with signature is c, and is sent to the cloud. The cloud
verifies the signature and stores the ciphertext C. When a reader wants to read, the
cloud sends C. If the user has attributes matching with access policy, it can decrypt
and get back original message.
Verify:
The verification process to the cloud, it relieves the individual users from time
consuming verifications. When a reader wants to read some data stored in the cloud, it
tries to decrypt it using the secret keys it receives from the KDCs.

2.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

41
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
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

42
 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.

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:

43
 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.
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.

44
RESULT AND CONCLUSION

3.1 APPENDICES

3.1.1 SAMPLE CODE

DATABASE:

package pack;

import java.sql.Connection;

import java.sql.DriverManager;

//import java.util.concurrent.ExecutionException;

//import javax.swing.JOptionPane;

public class Db {

public static Connection getConnection(){

Connection con =null;

try{

String url="jdbc:mysql://localhost:3306/decen";

String driver="com.mysql.jdbc.Driver";

Class.forName(driver).newInstance();

con = DriverManager.getConnection(url, "root", "root");

System.out.println("Database Connected");

catch(Exception e)

return con;

public static void main(String[] args) { }

45
NEW SERVLET:

package pack;

import java.io.BufferedReader;

import java.io.IOException;

import java.io.InputStream;

import java.io.InputStreamReader;

import java.io.PrintWriter;

import java.sql.Connection;

import java.sql.DriverManager;

import java.sql.PreparedStatement;

import java.util.Iterator;

import java.util.List;

import java.util.logging.Level;

import java.util.logging.Logger;

import javax.servlet.ServletException;

import javax.servlet.http.HttpServlet;

import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;

import org.apache.commons.fileupload.FileItem;

import org.apache.commons.fileupload.FileItemFactory;

import org.apache.commons.fileupload.FileUploadException;

import org.apache.commons.fileupload.disk.DiskFileItemFactory;

import org.apache.commons.fileupload.servlet.ServletFileUpload;

public class NewServlet extends HttpServlet {

private static java.sql.Date getCurrentDate() {

java.util.Date today = new java.util.Date();

return new java.sql.Date(today.getTime());

46
 }

protected void processRequest(HttpServletRequest request, HttpServletResponse

response)

throws ServletException, IOException {

response.setContentType("text/html;charset=UTF-8");

PrintWriter out = response.getWriter();

Connection con;

PreparedStatement pstm = null;

String subject = "";

String cd = "";

String a = (String) request.getSession().getAttribute("c");

System.out.println("User Name"+a);

try {

boolean isMultipartContent = ServletFileUpload.isMultipartContent(request);

if (!isMultipartContent) {

return;

FileItemFactory factory = new DiskFileItemFactory();

ServletFileUpload upload = new ServletFileUpload(factory);

try {

List<FileItem> fields = upload.parseRequest(request);

Iterator<FileItem> it = fields.iterator();

if (!it.hasNext()) {

return;

while (it.hasNext()) {

47
 FileItem fileItem = it.next();

if (fileItem.getFieldName().equals("subject")) {

subject = fileItem.getString();

System.out.println("Subject" + subject);

} else {

boolean isFormField = fileItem.isFormField();

if (isFormField) {

} else {

try {

Class.forName("com.mysql.jdbc.Driver");

con =
DriverManager.getConnection("jdbc:mysql://localhost:3306/decen", "root",
"root");

pstm = con.prepareStatement("insert into files

(file,subject,filetype,filename,CDate,owner,size,data)values(?,?,?,?,?,?,?,?)");

System.out.println("getD " + fileItem.getName());

String str = getStringFromInputStream(fileItem.getInputStream());

String cipher = new TrippleDes().encrypt(str);

System.out.println(str);

//for get extension from given file

String b = fileItem.getName().subs
tring(fileItem.getName().lastIndexOf('.'));

System.out.println("File Extension"+b);

pstm.setBinaryStream(1, fileItem.getInputStream());

pstm.setString(2, subject);

pstm.setString(3, b);

pstm.setString(4, fileItem.getName());

pstm.setDate(5, getCurrentDate());
48
 pstm.setString(6, a);

pstm.setLong(7, fileItem.getSize());

pstm.setString(8, cipher);

int i = pstm.executeUpdate();

if (i == 1) {

response.sendRedirect("fileupload.jsp?msg= sucess..!");

} else {

response.sendRedirect("fileupload.jsp?msgg= NOT sucess..!");

con.close();

} catch (Exception e) {

out.println(e.toString());

} catch (FileUploadException e) {

e.printStackTrace();

} catch (Exception ex) {

Logger.getLogger(NewServlet.class.getName()).log(Level.SEVERE, null,
ex);

} finally {

out.close(); }

private static String getStringFromInputStream(InputStream is) {

BufferedReader br = null;

StringBuilder sb = new StringBuilder();

49
 String line;

try {

br = new BufferedReader(new InputStreamReader(is));

while ((line = br.readLine()) != null) {

sb.append(line + "\n"); }

} catch (IOException e) {

e.printStackTrace();

} finally {

if (br != null) {

try {

br.close();

} catch (IOException e) {

e.printStackTrace();

SIMPLEFTP CLIENT:

50
package pack;

/**

* @author JP9-PC

*/

import java.net.*;

import java.io.*;

public class SimpleFTPClient {

/** The URL connection object */

private URLConnection m_client;

/** The FTP host/server to be connected */

private String host;

/** The FTP user */

private String user;

/** The FTP user’s password */

private String password;

/** The remote file that needs to be uploaded or downloaded */

private String remoteFile;

/** The previous error message triggered after a method is called */

private String erMesg;

/** The previous success message after any method is called */

private String succMesg;

public SimpleFTPClient() {

51
 /** Setter method for the FTP host/server */

public void setHost(String host) {

this.host = host;

/** Setter method for the FTP user */

public void setUser(String user) {

this.user = user;

/** Setter method for the FTP user’s password */

public void setPassword(String p) {

this.password = p;

/** Setter method for the remote file, this must include the sub-directory path
relative

to the user’s home directory, e.g you’e going to download a file that is within a sub
directory

called "sdir", and the file is named "d.txt", so you shall include the path as
"sdir/d.txt"

*/

public void setRemoteFile(String d) {

this.remoteFile = d;

/** The method that returns the last message of success of any method call */

public synchronized String getLastSuccessMessage() {

if (succMesg == null) {

return "";

return succMesg;

52
 }

/** The method that returns the last message of error resulted from any exception
of any method call */

public synchronized String getLastErrorMessage() {

if (erMesg == null) {

return "";

return erMesg;

/** The method that handles file uploading, this method takes the absolute file path

of a local file to be uploaded to the remote FTP server, and the remote file will then

be transfered to the FTP server and saved as the relative path name specified in
method setRemoteFile

@param localfilename – the local absolute file name of the file in local hard drive
that needs to

FTP over

*/

public synchronized boolean uploadFile(InputStream is) {

//public synchronized boolean uploadFile(String localfilename) {

try {

// InputStream is = new FileInputStream(localfilename);

BufferedInputStream bis = new BufferedInputStream(is);

OutputStream os = m_client.getOutputStream();

BufferedOutputStream bos = new BufferedOutputStream(os);

byte[] buffer = new byte[1024];

int readCount;

while ((readCount = bis.read(buffer)) > 0) {

53
 bos.write(buffer, 0, readCount);

bos.close();

this.succMesg = "Uploaded!";

return true;

} catch (Exception ex) {

ex.printStackTrace();

StringWriter sw0 = new StringWriter();

PrintWriter p0 = new PrintWriter(sw0, true);

ex.printStackTrace(p0);

erMesg = sw0.getBuffer().toString();

return false;

/** The method to download a file and save it onto the local drive of the client in
the specified absolut path

@param localfilename – the local absolute file name that the file needs to be saved
as */

public synchronized boolean downloadFile(String localfilename) {

try {

InputStream is = m_client.getInputStream();

BufferedInputStream bis = new BufferedInputStream(is);

System.out.println(">>>>>>>>>>>"+localfilename);

OutputStream os = new FileOutputStream(localfilename);

BufferedOutputStream bos = new BufferedOutputStream(os);

byte[] buffer = new byte[1024];

int readCount; while ((readCount = bis.read(buffer)) > 0) {

54
 bos.write(buffer, 0, readCount);

bos.close();

is.close(); // close the FTP inputstream

this.succMesg = "Downloaded!";

return true;

} catch (Exception ex) {

ex.printStackTrace();

StringWriter sw0 = new StringWriter();

PrintWriter p0 = new PrintWriter(sw0, true);

ex.printStackTrace(p0);

erMesg = sw0.getBuffer().toString();

return false;

/** The method that connects to the remote FTP server */

public synchronized boolean connect() {

try {

URL url = new URL("ftp://" + user + ":" + password + "@" + host + "/" +
remoteFile + ";type=i");

m_client = url.openConnection();

System.out.println(">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>.."+"ftp://"
+ user + ":" + password + "@" + host + "/" + remoteFile + ";type=i");

return true;

} catch (Exception ex) {

ex.printStackTrace();

StringWriter sw0 = new StringWriter();

55
 PrintWriter p0 = new PrintWriter(sw0, true);

ex.printStackTrace(p0);

erMesg = sw0.getBuffer().toString();

return false;

public static void main(String arg[]) {

SimpleFTPClient f = new SimpleFTPClient();

f.setHost("ftp.drivehq.com");

f.setUser("drive05");

f.setPassword("drive15");

f.setRemoteFile("c.txt");

boolean connected = f.connect();

TRIPPLEDES:

Package pack;

import java.security.spec.KeySpec;

import javax.crypto.Cipher;

import javax.crypto.SecretKey;

import javax.crypto.SecretKeyFactory;

import javax.crypto.spec.DESedeKeySpec;

import org.apache.commons.codec.binary.Base64;

/**

* @author AKHIL

56
*/

public class TrippleDes {

private static final String UNICODE_FORMAT = "UTF8";

public static final String DESEDE_ENCRYPTION_SCHEME =

"DESede";

private KeySpec ks;

private SecretKeyFactory skf;

private Cipher cipher;

byte[] arrayBytes;

private String myEncryptionKey;

private String myEncryptionScheme;

SecretKey key;

public TrippleDes() throws Exception {

myEncryptionKey = "ThisIsSpartaThisIsSparta";

myEncryptionScheme = DESEDE_ENCRYPTION_SCHEME;

arrayBytes = myEncryptionKey.getBytes(UNICODE_FORMAT);

ks = new DESedeKeySpec(arrayBytes);

skf = SecretKeyFactory.getInstance(myEncryptionScheme);

cipher = Cipher.getInstance(myEncryptionScheme);

key = skf.generateSecret(ks);

public String encrypt(String unencryptedString) {

String encryptedString = null;

try {

cipher.init(Cipher.ENCRYPT_MODE, key);

byte[] plainText =

unencryptedString.getBytes(UNICODE_FORMAT);

57
 byte[] encryptedText = cipher.doFinal(plainText);

encryptedString = new String(Base64.encodeBase64(encryptedText));

} catch (Exception e) {

e.printStackTrace();

return encryptedString;

public String decrypt(String encryptedString) {

String decryptedText = null;

try {

cipher.init(Cipher.DECRYPT_MODE, key);

byte[] encryptedText = Base64.decodeBase64(encryptedString);

byte[] plainText = cipher.doFinal(encryptedText);

decryptedText = new String(plainText);

} catch (Exception e) {

e.printStackTrace();

return decryptedText;

58
MAIL:
package pack;

//import com.sun.mail.smtp.SMTPTransport;

import java.util.Properties;

import javax.mail.Message;

import javax.mail.MessagingException;

import javax.mail.PasswordAuthentication;

import javax.mail.Session;

import javax.mail.Transport;

//import javax.mail.URLName;

import javax.mail.internet.InternetAddress;

import javax.mail.internet.MimeMessage;

public class mail_Senddd {

public static boolean sendMail(String msg, String userid, String to) {

Properties props = new Properties();

props.put("mail.smtp.host", "smtp.gmail.com");

props.put("mail.smtp.socketFactory.port", "465");

props.put("mail.smtp.socketFactory.class",

"javax.net.ssl.SSLSocketFactory");

props.put("mail.smtp.auth", "true");

props.put("mail.smtp.port", "465");

// Assuming you are sending email from localhost

Session session = Session.getDefaultInstance(props,

new javax.mail.Authenticator() {

@Override

protected PasswordAuthentication getPasswordAuthentication() {

return new PasswordAuthentication("", "");

59
 }

});

System.out.println("Message " + msg);

try {

Message message = new MimeMessage(session);

message.setFrom(new InternetAddress(userid));

message.setRecipients(Message.RecipientType.TO,

InternetAddress.parse(to));

message.setSubject("Secret key ");

message.setText(msg);

Transport.send(message);

System.out.println("Done");

return true;

catch (MessagingException e) {

System.out.println(e);

e.printStackTrace();

return false;

// throw new RuntimeException(e);

} public static void main(String arg[]) {

// sendMail("sssssssssss");

}}

60
3.1.2 SCREEN SHOT:

SIGNUP

61
ADMIN

62
USER DETAILS

63
KDC

64
TRUSTEE

65
LOGIN

66
YYYYYY

67
FILE DETAILS

68
REQUEST DETALS

69
3.2 CONCLUSION

We have presented a decentralized access control technique with anonymous

authentication, which provides user revocation and prevents replay attacks. The cloud
does not know the identity of the user who stores information, but only verifies the
user’s credentials. Key distribution is done in a decentralized way. One limitation is
that the cloud knows the access policy for each record stored in the cloud. In future,
we would like to hide the attributes and access policy of a user.

70
3.3 REFERENCES
[1] S. Ruj, M. Stojmenovic, and A. Nayak, “Privacy Preserving Access Control with
Authentication for Securing Data in Clouds,” Proc. IEEE/ACM Int’l Symp. Cluster,
Cloud and Grid Computing, pp. 556-563, 2012.

[2] C. Wang, Q. Wang, K. Ren, N. Cao, and W. Lou, “Toward Secure and
Dependable Storage Services in Cloud Computing,” IEEE Trans. Services
Computing, vol. 5, no. 2, pp. 220-232, Apr.- June 2012.

[3] J. Li, Q. Wang, C. Wang, N. Cao, K. Ren, and W. Lou, “Fuzzy Keyword Search
Over Encrypted Data in Cloud Computing,” Proc. IEEE INFOCOM, pp. 441-445,
2010.

[4] S. Kamara and K. Lauter, “Cryptographic Cloud Storage,” Proc. 14th Int’l Conf.
Financial Cryptography and Data Security, pp. 136- 149, 2010.

[5] H. Li, Y. Dai, L. Tian, and H. Yang, “Identity-Based Authentication for Cloud
Computing,” Proc. First Int’l Conf. Cloud Computing (CloudCom), pp. 157-166,
2009.

[6] C. Gentry, “A Fully Homomorphic Encryption Scheme,” PhD dissertation,

Stanford Univ., http://www.crypto.stanford.edu/ craig, 2009.

[7] A.-R. Sadeghi, T. Schneider, and M. Winandy, “Token-Based Cloud Computing,”

Proc. Third Int’l Conf. Trust and Trustworthy Computing (TRUST), pp. 417-429,
2010.

[8] R.K.L. Ko, P. Jagadpramana, M. Mowbray, S. Pearson, M. Kirchberg, Q. Liang,

and B.S. Lee, “Trustcloud: A Framework for Accountability and Trust in Cloud
Computing,” HP Technical Report HPL-2011-38,
http://www.hpl.hp.com/techreports/2011/HPL-2011-38.html, 2013.

71
[9] R. Lu, X. Lin, X. Liang, and X. Shen, “Secure Provenance: The Essential of Bread
and Butter of Data Forensics in Cloud Computing,” Proc. Fifth ACM Symp.
Information, Computer and Comm. Security (ASIACCS), pp. 282-292, 2010.

[10] D.F. Ferraiolo and D.R. Kuhn, “Role-Based Access Controls,” Proc. 15th Nat’l
Computer Security Conf., 1992.

[11] D.R. Kuhn, E.J. Coyne, and T.R. Weil, “Adding Attributes to Role-Based Access
Control,” IEEE Computer, vol. 43, no. 6, pp. 79-81, June 2010.

[12] M. Li, S. Yu, K. Ren, and W. Lou, “Securing Personal Health Records in Cloud
Computing: Patient-Centric and Fine-Grained Data Access Control in Multi-Owner
Settings,” Proc. Sixth Int’l ICST Conf. Security and Privacy in Comm. Networks
(SecureComm), pp. 89-106, 2010.

[13] S. Yu, C. Wang, K. Ren, and W. Lou, “Attribute Based Data Sharing with
Attribute Revocation,” Proc. ACM Symp. Information, Computer and Comm.
Security (ASIACCS), pp. 261-270, 2010.

[14] G. Wang, Q. Liu, and J. Wu, “Hierarchical Attribute-Based Encryption for Fine-
Grained Access Control in Cloud Storage Services,” Proc. 17th ACM Conf. Computer
and Comm. Security (CCS), pp. 735-737, 2010.

72