CSEIT11831452 | Proficient Public Substantiation of Data Veracity for Cloud Storage through Dual Protection release_rev_e6fa8810-8cc0-4a74-8996-48037b74a2c1

by Ajay Kannan

Released as a article-journal .

Abstract

The cloud security is one of the important roles in cloud, here we can preserve our data into cloud storage. More and more clients would like to store their data to PCS (public cloud servers) along with the rapid development of cloud computing. Cloud storage services allow users to outsource their data to cloud servers to save local data storage costs. Multiple verification tasks from different users can be performed efficiently by the auditor and the cloud-stored data can be updated dynamically. It makes the clients check whether their outsourced data is kept intact without downloading the whole data. In our system we are using the own auditing based on the token generation. Using this key generation technique compare the key values from original keys we can find out the changes about the file. A novel public verification scheme for cloud storage using in distinguishability obfuscation, which requires a lightweight computation on the auditor and delegate most computation to the cloud. Not only stored also the content will be encrypted in the cloud server. If anyone try to hack at the cloud end is not possible to break the two different blocks. The security of our scheme under the strongest security model. They need first decrypt the files and also combine the splitted files from three different locations. This is not possible by anyone. Anyone can download the files from the server with file owner permission. At the time of download key generated (code based key generation) and it will send to the file owner. We can download the file need to use the key for verification and some other users want to download file owner permission is necessary.
In text/plain format

Type  article-journal
Stage   unknown
Work Entity
access all versions, variants, and formats of this works (eg, pre-prints)
Revision

This is a specific, static metadata record, not necessarily linked to any current entity in the catalog.

Catalog Record
Revision: e6fa8810-8cc0-4a74-8996-48037b74a2c1
API URL: JSON