Panda:
Public Auditing for Shared Data with Efficient User
Revocation
in the Cloud
ABSTRACT
With data
storage and sharing services in the cloud, users can easily modify and share
data as a group. To ensure share data integrity can be verified publicly, users
in the group need to compute signatures on all the blocks in shared data.
Different blocks in shared data are generally signed by different users due to
data modifications performed by different users. For security reasons, once a
user is revoked from the group, the blocks which were previously signed by this
revoked user must be re-signed by an existing user. The straight forward
method, which allows an existing user to download the corresponding part of
shared data and re-sign it during user revocation, is inefficient due to the
large size of shared data in the cloud. In this paper, we propose a novel
public auditing mechanism
For
the integrity of shared data with efficient user revocation in mind. By
utilizing the idea of proxy re-signatures, we allow the cloud tore-sign blocks
on behalf of existing users during user revocation, so that existing users do
not need to download and re-sign blocks by themselves. In addition, a public
verifier is always able to audit the integrity of shared data without
retrieving the entire data from the
Cloud,
even if some part of shared data has been re-signed by the cloud. Moreover, our
mechanism is able to support batch auditing by verifying multiple auditing
tasks simultaneously. Experimental results show that our mechanism can
significantly improve the efficiency of user revocation.
Existing System:
An
existing system the file uploaded in cloud which not signed by user in each
time of upload. So that integrity of shared data is not possible
in existing system. However, since the cloud is not in the same trusted domain
with each user in the group, outsourcing every user’s private key to the cloud
would introduce significant security issue.
Proposed System:
In
our Proposed system may lie to verifiers about the incorrectness of shared data
in order to save the reputation of its data services and avoid losing money on
its data services. In addition, we also assume there is no collusion between
the cloud and any user during the design of our mechanism. Generally, the
incorrectness of share data under the above semi trusted model can be
introduced by hardware/software failures or human errors happened in the cloud.
Considering these factors, users do not fully trust the cloud with the
integrity of shared data.
Advantage:
1.Blocking User account
2.Security
question
3.Login
with secret key in each time
SYSTEM ARCHITECTURE:
SYSTEM SPECIFICATION
Hardware
Requirements:
•
System : Pentium IV 2.4 GHz.
•
Hard Disk
: 40 GB.
•
Floppy Drive :
1.44 Mb.
•
Monitor
: 14’ Colour Monitor.
•
Mouse : Optical Mouse.
•
Ram :
512 Mb.
Software
Requirements:
•
Operating
system : Windows 7.
•
Coding
Language : ASP.Net with C#
•
Data Base :
SQL Server 2008.
No comments:
Post a Comment