DATA INTEGRITY PROOFS IN CLOUD STORAGE

Project work
Submitted by

PIJUSH NATH ( Reg. No: !!"#""## $

In partial fulfillment of the requirement for the award of the Degree of

%ASTER OF CO%PUTER APPLICATION

Under the guidance of

%r&. CHRISTRY ANGELINE %.C.A' %.P()*.

Asst.Professor Trichy

DEPART%ENT OF CO%PUTER APPLICATIONS PRIST UNI+ERSITY Ce,ter -or H)g(er Le.r,),g / Re&e.rc( TRICHY CA%PUS 0TA%IL NADU %ARCH1"#!2

AC3NO4LEDGE%ENTS

I wish to thank the almighty for gi ing me such an opportunity. I e!press my sincere gratitude to my parents who steadfastly behind me in all my effort to the successful completion of this pro"ect. I am deeply indebted to my guide and #od of $%A department $rs.S.%hristy Angeline& $%A& $.Phil& Assistant professor& Prist Uni ersity& Trichy whose help& stimulating suggestions and encouragement throughout this pro"ect. I wish to thank all my staff member of our department who helped me a lot for successful completion of this pro"ect. 'inally& I would like to ha e a mention of thanks to my parents and friends who ga e us the moral strength and encouragement for completion my pro"ect successfully. (e are greatly thanked to our lab Assistants& who were patience and always helped us when we are in need. (e are ery much thankful to our parents and friends for their moral support and for their lo e and prayer throughout our studies. (e thank all our friends and well)wishers who helped us and who were a shoulder to us to learn on when we were discouraged.

PI*US# +AT#

PRIST UNI+ERSITY (U5& o- UGC Act !67 $ Tr)c(8 C.9:;& S. %hristy Angeline &$%A&$.Phil Assistant Professor Department of %omputer Application Prist Uni ersity Trichy <ONA1FIDE CERTIFICATE

This is to certify that the Pro"ect work as, Image Processing -ased .n (atermarking Picture $aker, is the bonafide record of the pro"ect work done by $r. PI*US# +AT#& /01 +.234456556663 in partial fulfillment for the award of the Degree of $aster Application during the academic year 5645)5647. The work done under the guidance and super ision of $rs. S. %hristy Angeline & $%A& $.Phil.

Signature of the Head of the Department (S. Christy Angelina

Signature of the Guide

External Examiner

CHAPTER #!

A<STRACT:
%loud computing has been en isioned as the de)facto solution to the rising storage costs of IT 0nterprises. (ith the high costs of data storage de ices as well as the rapid rate at which data is being generated it pro es costly for enterprises or indi idual users to frequently update their hardware. Apart from reduction in storage costs data outsourcing to the cloud also helps in reducing the maintenance. %loud storage mo es the user8s data to large data centers& which are remotely located& on which user does not ha e any control. #owe er& this unique feature of the cloud poses many new security challenges& which need to be clearly understood and resol ed. (e pro ide a scheme& which gi es a proof of data integrity in the cloud& which the customer can employ to check the correctness of his data in the cloud. This proof can be agreed upon by both the cloud and the customer and can be incorporated in the Ser ice le el agreement 9S:A;.

PROJECT PURPOSE:
Purpose of de eloping proofs for data possession at untrusted cloud storage ser ers we are often limited by the resources at the cloud ser er as well as at the client. 1i en that the data si<es are large and are stored at remote ser ers& accessing the entire file can be e!pensi e in I=. costs to the storage ser er. Also transmitting the file across the network to the client can consume hea y bandwidths. Since growth in storage capacity has far outpaced the growth in data access as well as network bandwidth& accessing and transmitting the entire archi e e en occasionally greatly limits the scalability of the network resources. 'urthermore& the I=. to establish the data proof interferes with the on) demand bandwidth of the ser er used for normal storage and retrie ing purpose.

PROJECT SCOPE:
%loud storing its data file ' at the client should process it and create suitable meta data which is used in the later stage of erification the data integrity at the cloud storage. (hen checking for data integrity the client queries the cloud storage for suitable replies based on which it concludes the integrity of its data stored in the client. our data integrity protocol the erifier needs to store only a single cryptographic key ) irrespecti e of the si<e of the data file ') and two functions which generate a random sequence. The erifier does not store any data with it. The erifier before storing the file at the archi e& preprocesses the file and appends some meta data to the file and stores at the archi e.

PRODUCT FEATURES:
.ur scheme was de eloped to reduce the computational and storage o erhead of the client as well asto minimi<e the computational o erhead of the cloud storage ser er. (e also minimi<ed the si<e of the proof of data integrity so as to reduce the network bandwidth consumption. #ence the storage at the client is ery much minimal compared to all other schemes that were de eloped. #ence this scheme pro es ad antageous to thin clients like PDAs and mobile phones. The operation of encryption of data generally consumes a large computational power. In our scheme the encrypting process is ery much limited to only a fraction of the whole data thereby sa ing on the computational time of the client. $any of the schemes proposed earlier require the archi e to perform tasks that need a lot of computational power to generate the proof of data integrity. -ut in our scheme the archi e "ust need to fetch and send few bits of data to the client.

INTRODUCTION:
Data outsourcing to cloud storage ser ers is raising trend among many firms and users owing to its economic ad antages. This essentially means that the owner 9client; of the data mo es its data to a third party cloud storage ser er which is supposed to ) presumably for a fee ) faithfully store the data with it and pro ide it back to the owner whene er required. As data generation is far outpacing data storage it pro es costly for small firms to frequently update their hardware whene er additional data is created. Also maintaining the storages can be a difficult task. Storage outsourcing of data to cloud storage helps such firms by reducing the costs of storage& maintenance and personnel. It can also assure a reliable storage of important data by keeping multiple copies of the data thereby reducing the chance of losing data by hardware failures. Storing of user data in the cloud despite its ad antages has many interesting security concerns& which need to be e!tensi ely in estigated for making it a reliable solution to the problem of a oiding local storage of data. In this paper we deal with the problem of implementing a protocol for obtaining a proof of data possession in the cloud sometimes referred to as Proof of irretrie ability 9P./;. This problem tries to obtain and erify a proof that the data that is stored by a user at remote data storage in the cloud 9called cloud storage archi es or simply archi es; is not modified by the archi e and thereby the integrity of the data is assured. Such erification systems pre ent the cloud storage archi es from misrepresenting or modifying the data stored at it without the consent of the data owner by using frequent checks on the storage archi es. Such checks must allow the data owner to efficiently& frequently& quickly and securely erify that the cloud archi e is not cheating the owner. %heating& in this conte!t& means that the storage archi e might delete some of the data or may modify some of the data.

CHAPTER #" SYSTE% ANALYSIS: PRO<LE% DEFINITION:

Storing of user data in the cloud despite its ad antages has many interesting security concerns which need to be e!tensi ely in estigated for making it a reliable solution to the problem of a oiding local storage of data. $any problems like data authentication and integrity 9i.e.& how to efficiently and securely ensure that the cloud storage ser er returns correct and complete results in response to its clients8 queries& outsourcing encrypted data and associated difficult problems dealing with querying o er encrypted domain were discussed in research literature.

E=ISTING SYSTE%:
As data generation is far outpacing data storage it pro es costly for small firms to frequently update their hardware whene er additional data is created. Also maintaining the storages can be a difficult task. It transmitting the file across the network to the client can consume hea y bandwidths. The problem is further complicated by the fact that the owner of the data may be a small de ice& like a PDA 9personal digital assist; or a mobile phone& which ha e limited %PU power& battery power and communication bandwidth.

LI%ITATIONS OF E=ISTING SYSTE%:

The main drawback of this scheme is the high resource costs it requires for Also computing hash alue for e en a moderately large data files can be Data encryption is large so the disad antage is small users with limited

the implementation. computationally burdensome for some clients 9PDAs& mobile phones& etc;. computational power 9PDAs& mobile phones etc.;.

PROPOSED SYSTE%:
.ne of the important concerns that need to be addressed is to assure the customer of the integrity i.e. correctness of his data in the cloud. As the data is physically not accessible to the user the cloud should pro ide a way for the user to check if the integrity of his data is maintained or is compromised. In this paper we pro ide a scheme& which gi es a proof of data integrity in the cloud& which the customer can employ to check the correctness of his data in the cloud. This proof can be agreed upon by both the cloud and the customer and can be incorporated in the Ser ice le el agreement 9S:A;. It is important to note that our proof of data integrity protocol "ust checks the integrity of data i.e. if the data has been illegally modified or deleted.

AD+ANTAGES OF PROPOSED SYSTE%:

Apart from reduction in storage costs data outsourcing to the cloud also helps in

reducing the maintenance. A oiding local storage of data. -y reducing the costs of storage& maintenance and personnel. It reduces the chance of losing data by hardware failures. +ot cheating the owner.

PROCESS FLO4 DIAGRA%S FOR E=ISTING AND PROPOSED SYSTE%: FEASI<ILITY STUDY:
The feasibility of the pro"ect is analy<ed in this phase and business proposal is put forth with a ery general plan for the pro"ect and some cost estimates. During 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. 'or feasibility analysis& some understanding of the ma"or requirements for the system is essential. Three key considerations in ol ed in the feasibility analysis are 0%.+.$I%A: '0ASI-I:IT> T0%#+I%A: '0ASI-I:IT> S.%IA: '0ASI-I:IT>

ECONO%ICAL FEASI<ILITY: This study is carried out to check the economic impact that the system will ha e on the organi<ation. The amount of fund that the company can pour into the research and de elopment of the system is limited. The e!penditures must be "ustified. Thus the de eloped system as well within the budget and this was achie ed because most of the technologies used are freely a ailable. .nly the customi<ed products had to be purchased. TECHNICAL FEASI<ILITY This study is carried out to check the technical feasibility& that is& the technical requirements of the system. Any system de eloped must not ha e a high demand on the a ailable technical resources. This will lead to high demands on the a ailable technical resources. This will lead to high demands being placed on the client. The de eloped system must ha e a modest requirement& as only minimal or null changes are required for implementing this system.

HARD4ARE AND SOFT4ARE RE>UIRE%ENTS:

HARD4ARE RE>UIRE%ENTS:

? ? ? ? ? ?

System #ard Disk $onitor $ouse /am

2 2 2 2 2

Pentium I@ 5.7 1#<. 76 1-. 4.77 $b. 4A @1A %olour. :ogitech. A45 $b.

'loppy Dri e 2

SOFT4ARE RE>UIRE%ENTS:

? ? ?

.perating system %oding :anguage Data -ase

2 (indows BP. 2 ASP.+et with %C 2 SD: Ser er 56#7

FUNCTIONAL RE>UIRE%ENTS:
'unctional requirements specify which output file should be produced from the gi en file they describe the relationship between the input and output of the system& for each functional requirement a detailed description of all data inputs and their source and the range of alid inputs must be specified.

NON FUNCTIONAL RE>UIRE%ENTS:

Describe user) isible aspects of the system that are not directly related with the functional beha ior of the system. +on)'unctional requirements include quantitati e constraints& such as response time 9i.e. how fast the system reacts to user commands.; or accuracy 99.e. how precise are the systems numerical answers.;

PSEUDO RE>UIRE%ENTS:
The client that restricts the implementation of the system imposes these requirements. Typical pseudo requirements are the implementation language and the platform on which the system is to be implemented. These ha e usually no direct effect on the users iew of the system.

LITERATURE SUR+EY:
:iterature sur ey is the most important step in software de elopment process. -efore de eloping the tool it is necessary to determine the time factor& economy n company strength. .nce these things r satisfied& ten ne!t steps is to determine which operating system and language can be used for de eloping the tool. .nce the programmers start building the tool the programmers need lot of e!ternal support. This support can be obtained from senior programmers& from book or from websites. -efore building the system the abo e consideration r taken into account for de eloping the proposed system.

(e ha e to analysis the C*o;? Co9:;t),g O;t*),e S;r@e82 C*o;? Co9:;t),g %loud computing pro iding unlimited infrastructure to store and e!ecute customer

data and program. As customers you do not need to own the infrastructure& they are merely accessing or rentingE they can forego capital e!penditure and consume resources as a ser ice& paying instead for what they use. <e,e-)t& o- C*o;? Co9:;t),g: $inimi<ed %apital e!penditure :ocation and De ice independence Utili<ation and efficiency impro ement @ery high Scalability #igh %omputing power

Sec;r)t8 . 9.jor Co,cer,: Security concerns arising because both customer data and program are residing in Security is always a ma"or concern in .pen System Architectures

Pro ider Premises.

D.t. ce,tre Sec;r)t8A Professional Security staff utili<ing ideo sur eillance& state of the art intrusion (hen an employee no longer has a business need to access datacenter his All physical and electronic access to data centers by employees should be logged Audit tools so that users can easily determine how their data is stored& protected&

detection systems& and other electronic means. pri ileges to access datacenter should be immediately re oked. and audited routinely. used& and erify policy enforcement.

D.t. Loc.t)o,: (hen user uses the cloud& user probably wonFt know e!actly where your data is Data should be stored and processed only in specific "urisdictions as define by hosted& what country it will be stored inG user.

Pro ider should also make a contractual commitment to obey local pri acy Data)centered policies that are generated when a user pro ides personal or

requirements on behalf of their customers& sensiti e information& that tra els with that information throughout its lifetime to ensure that the information is used only in accordance with the policy

<.ck;:& o- D.t. :

Data store in database of pro ider should be redundantly store in multiple Data that is generated during running of program on instances is all customer %ontrol of Administrator on Databases.

physical location. data and therefore pro ider should not perform backups.

Network Sec;r)t8: De,).* o- Ser@)ce2 where ser ers and networks are brought down by a huge

amount of network traffic and users are denied the access to a certain Internet based ser ice. L)ke DNS H.ck),g& /outing Table HPoisoning,& BDoS attacks >oS +)o*.t)o, 2 through congestion& delaying or dropping packets& or through

resource hacking.

%., ), t(e %)??*e Att.ck2 To o ercome it always use SS: IP S:oo-),g2 Spoofing is the creation of T%P=IP packets using somebody elseFs IP So*;t)o,2 Infrastructure will not permit an instance to send traffic with a source IP

address. or $A% address other than its own.

How &ec;re )& e,cr8:t)o, Sc(e9e: Is it possible for all of my data to be fully encryptedG (hat algorithms are usedG (ho holds& maintains and issues the keysG Problem2 0ncryption accidents can make data totally unusable. 0ncryption can complicate a ailability Solution The cloud pro ider should pro ide e idence that encryption schemes were

designed and tested by e!perienced specialists. I,-or9.t)o, Sec;r)t8: Security related to the information e!changed between different hosts or between This issues pertaining to secure communication, authentication, and issues Secure communication issues include those security concerns that arise during the These include confidentiality and integrity issues. %onfidentiality indicates that all

hosts and users. concerning single sign on and delegation. communication between two entities. data sent by users should be accessible to only Hlegitimate, recei ers& and integrity indicates that all data recei ed should only be sent=modified by Hlegitimate, senders. So*;t)o,: public key encryption& B.A6I certificates& and the Secure Sockets :ayer 9SS:; enables secure authentication and communication o er computer networks.

%ODULES DESCRIPTION:
CLOUD STORAGE: Data outsourcing to cloud storage ser ers is raising trend among many firms and users owing to its economic ad antages. This essentially means that the owner 9client; of the data mo es its data to a third party cloud storage ser er which is supposed to ) presumably for a fee ) faithfully store the data with it and pro ide it back to the owner whene er required. SI%PLY ARCHI+ES: This problem tries to obtain and erify a proof that the data that is stored by a user at remote data storage in the cloud 9called cloud storage archi es or simply archi es; is not modified by the archi e and thereby the integrity of the data is assured. %loud archi e is not cheating the owner& if cheating& in this conte!t& means that the storage archi e might delete some of the data or may modify some of the data SENTINELS: In this scheme& unlike in the key)hash approach scheme& only a single key can be used irrespecti e of the si<e of the file or the number of files whose retrie ability it wants to erify. Also the archi e needs to access only a small portion of the file ' unlike in the key)has scheme& which required the archi e to process the entire file ' for each protocol erification. If the pro er has modified or deleted a substantial portion of '& then with high probability it will also ha e suppressed a number of sentinels. +ERIFICATION PHASE: The erifier before storing the file at the archi e & preprocesses the file and appends some $eta data to the file and stores at the archi e. At the time of erification the erifier uses this $eta data to erify the integrity of the data. It is important to note that our proof of data integrity protocol "ust checks the integrity of data i.e. if the data has

been illegally modified or deleted. It does not pre ent the archi e from modifying the data.

CHAPTER #B SYSTE% DESIGN: D.t. F*ow D).gr.9 5 U&e C.&e D).gr.9 5 F*ow D).gr.9:
The D'D is also called as bubble chart. It is a simple graphical formalism

that can be used to represent a system in terms of the input data to the system& arious processing carried out on these data& and the output data is generated by the system The data flow diagram 9D'D; 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 e!ternal entity that interacts with the system and the information flows in the system. D'D shows how the information mo es through the system and how it is

modified by a series of transformations. It is a graphical technique that depicts information flow and the transformations that are applied as data mo es from input to output. D'D is also known as bubble chart. A D'D may be used to represent a system at

any le el of abstraction. D'D may be partitioned into le els that represent increasing information flow and functional detail.

SDLC: SPIRAL %ODEL: PROJECT ARCHITECTURE:

U%L DIAGRA%S: USE CASE:

Create Account

Login

File Upload

TPA

File !eri"y Owner Cryptography key Request

Admin

File

ownload

File etails

Owner

etails

CLASS:

Registration # Owner# Password )ender 'o*ile +'ail ate

File Archive File# File$ame File%i&e FilePath FileOwner 'eta ata (eyRequest ownload%tatus 'odi"y%tatus !eri"y%tatus metadatagenration() fileupload()

Loginidgenration() CreateAccount()

File Archive Modify File# File$ame File%i&e FilePath FileOwner 'eta ata (eyRequest !eri"y%tatus

comparemetadata() fileupload()

SE>UENCE:

!ata"ase Admin TPA O ner Create Account 'pload Files Cryptography (ncryption %ey

$erify O ner Files !iect $erify Files

!o nload $erification %ey re&uest !o nload %ey Re&uest Allo )*loc%

!o nload $erification)+ey Processing 'pload $rification File File Modify ,tatus !o nload File $ie O ner !etalils - O ner Files .arning To O ner .aring from Admin

!irect verification

!o nload verification

#ot Modify File

Modify File

ACTI+ITY:

Login

Admin

O ner

TPA

Admin

(/ists Create Account

File $erification

$ie

- !o nload o ner files File 'pload !irect $erification Cryptogrphic %ey ,ent to Mail %ey re&uest to o ner !o nload $erification

$ie O ner !etails

.arning Mail To O ner

ownload !eri"ication

$erifiction ,tatus

irect !eri"ication !o nload Re&uest ,tatus

Chec%

File #ot Modify File Modify

Process Pending

File #ot Modify

File !o nload ith %ey

File !o nload

File !o nload ith crypto %ey

do nload modify File ith %ey

$erify - 'pload !o nlod File

.arning from Admin

A

DFD DIAGRA%S:

Login

TPA

Admin

O ner

File $erification

$ie - !o nload O ner Files

(/ists Create Account

$ie O ner !etails !irect $erification !o nload $erification

File 'pload

.arning Mail To O ner

Cryptogrphic %ey ,ent to Mail

%ey re&uest to o ner

ownload !eri"ication

$erifiction ,tatus

irect !eri"ication

,lock
Process Pending

!o nload Re&uest ,tatus

Chec% File #ot Modify

File #ot Modify File Modify File !o nload ith %ey

Allow
File !o nload

$erify - 'pload !o nlod File

File !o nload ith crypto %ey

do nload modify File ith %ey

.arning from Admin

(nd

CHAPTER #2 PROCESS SPECIFICATION(Tec(,)C;e& A,? A*gor)t(9 U&e?$:

ALGORITH%: %ETA1DATA GENERATION: :et the erifier @ wishes to the store the file ' with the archi e. :et this file ' consist of n file blocks. (e initially preprocess the file and create metadata to be appended to the file. :et each of the n data blocks ha e m bits in them. A typical data file ' which the client wishes to store in the cloud. 0ach of the $eta data from the data blocks mi is encrypted by using a suitable algorithm to gi e a new modified $eta data $i. (ithout loss of generality we show this process by using a simple B./ operation. The encryption method can be impro ised to pro ide still stronger protection for erifier8s data. All the $eta data bit blocks that are generated using the abo e procedure are to be concatenated together. This concatenated $eta data should be appended to the file ' before storing it at the cloud ser er. The file ' along with the appended $eta data e ' is archi ed with the cloud.

SCREEN SHOTS:

O4NER

/egistration

.wner :ogin

.wner $ain

'ile Upload

'ile Status

'ile details

TPA Auditor :.1I+

TPA Auditor $ain

'ile @erification

'ile Direct @erification

Send $essage

.wner 'ile @iew

'ie Details

AD$I+ :.1I+

Admin $ain

0mail to .wner

.wner @iew

CHAPTER #7 TECHNOLOGY DESCRIPTION:

So-tw.re E,@)ro,9e,t FEATURES OF. NET $icrosoft .+0T is a set of $icrosoft software technologies for rapidly building and integrating B$: (eb ser ices& $icrosoft (indows)based applications& and (eb solutions. The .+0T 'ramework is a language)neutral platform for writing programs that can easily and securely interoperate. There8s no language barrier with .+0T2 there are numerous languages a ailable to the de eloper including $anaged %JJ& %C& @isual -asic and *a a Script. The .+0T framework pro ides the foundation for components to interact seamlessly& whether locally or remotely on different platforms. It standardi<es common data types and communications protocols so that components created in different languages can easily interoperate. H.+0T, is also the collecti e name gi en to arious software components built upon the .+0T platform. These will be both products 9@isual Studio.+0T and (indows.+0T Ser er& for instance; and ser ices 9like Passport& .+0T $y Ser ices& and so on;. THE .NET FRA%E4OR3 The .+0T 'ramework has two main parts2 4. The %ommon :anguage /untime 9%:/;. 5. A hierarchical set of class libraries. The %:/ is described as the He!ecution engine, of .+0T. It pro ides the en ironment within which programs run. The most important features are

 features.

%on ersion

from

low)le el

assembler)style

language&

called

Intermediate :anguage 9I:;& into code nati e to the platform being e!ecuted on. $emory management& notably including garbage collection. %hecking and enforcing security restrictions on the running code. :oading and e!ecuting programs& with ersion control and other such

The following features of the .+0T framework are also worth description2

%.,.ge? Co?e The code that targets .+0T& and which contains certain e!tra Information ) Hmetadata, ) to describe itself. (hilst both managed and unmanaged code can run in the runtime& only managed code contains the information that allows the %:/ to guarantee& for instance& safe e!ecution and interoperability. %.,.ge? D.t. (ith $anaged %ode comes $anaged Data. %:/ pro ides memory allocation and Deal location facilities& and garbage collection. Some .+0T languages use $anaged Data by default& such as %C& @isual -asic.+0T and *Script.+0T& whereas others& namely %JJ& do not. Targeting %:/ can& depending on the language you8re using& impose certain constraints on the features a ailable. As with managed and unmanaged code& one can ha e both managed and unmanaged data in .+0T applications ) data that doesn8t get garbage collected but instead is looked after by unmanaged code. Co99o, T8:e S8&te9 The %:/ uses something called the %ommon Type System 9%TS; to strictly enforce type)safety. This ensures that all classes are compatible with each other& by describing types in a common way. %TS define how types work within the runtime& which enables types in one language to interoperate with types in another language& including cross) language e!ception handling. As well as ensuring that types are only used in appropriate ways& the runtime also ensures that code doesn8t attempt to access memory that hasn8t been allocated to it.

Co99o, L.,g;.ge S:ec)-)c.t)o, The %:/ pro ides built)in support for language interoperability. To ensure that you can de elop managed code that can be fully used by de elopers using any programming language& a set of language features and rules for using them called the %ommon :anguage Specification 9%:S; has been defined. %omponents that follow these rules and e!pose only %:S features are considered %:S)compliant. THE CLASS LI<RARY: .+0T pro ides a single)rooted hierarchy of classes& containing o er K666 types. The root of the namespace is called SystemE this contains basic types like -yte& Double& -oolean& and String& as well as .b"ect. All ob"ects deri e from System. .b"ect. As well as ob"ects& there are alue types. @alue types can be allocated on the stack& which can pro ide useful fle!ibility. There are also efficient means of con erting alue types to ob"ect types if and when necessary. The set of classes is pretty comprehensi e& pro iding collections& file& screen& and network I=.& threading& and so on& as well as B$: and database connecti ity. The class library is subdi ided into a number of sets 9or namespaces;& each pro iding distinct areas of functionality& with dependencies between the namespaces kept to a minimum. LANGUAGES SUPPORTED <Y .NET The multi)language capability of the .+0T 'ramework and @isual Studio .+0T enables de elopers to use their e!isting programming skills to build all types of applications and B$: (eb ser ices. The .+0T framework supports new ersions of $icrosoft8s old fa orites @isual -asic and %JJ 9as @-.+0T and $anaged %JJ;& but there are also a number of new additions to the family.

@isual -asic .+0T has been updated to include many new and impro ed language features that make it a powerful ob"ect)oriented programming language. These features include inheritance& interfaces& and o erloading& among others. @isual -asic also now supports structured e!ception handling& custom attributes and also supports multi) threading. @isual -asic .+0T is also %:S compliant& which means that any %:S)compliant language can use the classes& ob"ects& and components you create in @isual -asic .+0T. $anaged 0!tensions for %JJ and attributed programming are "ust some of the enhancements made to the %JJ language. $anaged 0!tensions simplify the task of migrating e!isting %JJ applications to the new .+0T 'ramework. %C is $icrosoft8s new language. It8s a %)style language that is essentially H%JJ for /apid Application De elopment,. Unlike other languages& its specification is "ust the grammar of the language. It has no standard library of its own& and instead has been designed with the intention of using the .+0T libraries as its own.

$icrosoft @isual *C .+0T pro ides the easiest transition for *a a)language de elopers into the world of B$: (eb Ser ices and dramatically impro es the interoperability of *a a)language programs with e!isting software written in a ariety of other programming languages. Acti e State has created @isual Perl and @isual Python& which enable .+0T)aware applications to be built in either Perl or Python. -oth products can be integrated into the @isual Studio .+0T en ironment. @isual Perl includes support for Acti e State8s Perl De Lit. .ther languages for which .+0T compilers are a ailable include './T/A+ %.-.: 0iffel

'ig4 .+et 'ramework ASP.+0T (indows 'orms

B$: (0- S0/@I%0S -ase %lass :ibraries %ommon :anguage /untime .perating System

%C.+0T is also compliant with %:S 9%ommon :anguage Specification; and supports structured e!ception handling. %:S is set of rules and constructs that are supported by the %:/ 9%ommon :anguage /untime;. %:/ is the runtime en ironment pro ided by the .+0T 'rameworkE it manages the e!ecution of the code and also makes the de elopment process easier by pro iding ser ices. %C.+0T is a %:S)compliant language. Any ob"ects& classes& or components that created in %C.+0T can be used in any other %:S)compliant language. In addition& we can use ob"ects& classes& and components created in other %:S)compliant languages in %C.+0T .The use of %:S ensures complete interoperability among applications& regardless of the languages used to create the application.

CONSTRUCTORS AND DESTRUCTORS: %onstructors are used to initiali<e ob"ects& whereas destructors are used to destroy them. In other words& destructors are used to release the resources allocated to the ob"ect. In %C.+0T the sub finali<e procedure is a ailable. The sub finali<e procedure is used to complete the tasks that must be performed when an ob"ect is destroyed. The sub finali<e procedure is called automatically when an ob"ect is destroyed. In addition& the sub finali<e procedure can be called only from the class it belongs to or from deri ed classes.

GAR<AGE COLLECTION 1arbage %ollection is another new feature in %C.+0T. The .+0T 'ramework monitors allocated resources& such as ob"ects and ariables. In addition& the .+0T 'ramework automatically releases memory for reuse by destroying ob"ects that are no longer in use. In %C.+0T& the garbage collector checks for the ob"ects that are not currently in use by applications. (hen the garbage collector comes across an ob"ect that is marked for garbage collection& it releases the memory occupied by the ob"ect. O+ERLOADING . erloading is another feature in %C. . erloading enables us to define multiple procedures with the same name& where each procedure has a different set of arguments. -esides using o erloading for procedures& we can use it for constructors and properties in a class.

%ULTITHREADING: %C.+0T also supports multithreading. An application that supports multithreading can handle multiple tasks simultaneously& we can use multithreading to decrease the time taken by an application to respond to user interaction. STRUCTURED E=CEPTION HANDLING %C.+0T supports structured handling& which enables us to detect and remo e errors at runtime. In %C.+0T& we need to use TryM%atchM'inally statements to create e!ception handlers. Using TryM%atchM'inally statements& we can create robust and effecti e e!ception handlers to impro e the performance of our application. THE .NET FRA%E4OR3 The .+0T 'ramework is a new computing platform that simplifies application de elopment in the highly distributed en ironment of the Internet.

FEATURES OF S>L1SER+ER The .:AP Ser ices feature a ailable in SD: Ser er ersion K.6 is now called SD: Ser er 5666 Analysis Ser ices. The term .:AP Ser ices has been replaced with the term Analysis Ser ices. Analysis Ser ices also includes a new data mining component. The /epository component a ailable in SD: Ser er ersion K.6 is now called $icrosoft SD: Ser er 5666 $eta Data Ser ices. /eferences to the component now use the term $eta Data Ser ices. The term repository is used only in reference to the repository engine within $eta Data Ser ices SD:)S0/@0/ database consist of si! type of ob"ects& They are& 4. TA-:0 5. DU0/> N. './$ 7. /0P./T A. $A%/. TA<LE: A database is a collection of data about a specific topic. +IE4S OF TA<LE: (e can work with a table in two types& 4. Design @iew 5. Datasheet @iew De&)g, +)ew To build or modify the structure of a table we work in the table design iew. (e can specify what kind of data will be hold. D.t.&(eet +)ew To add& edit or analyses the data itself we work in tables datasheet iew mode.

>UERY: A query is a question that has to be asked the data. Access gathers data that answers the question from one or more table. The data that make up the answer is either dynaset 9if you edit it; or a snapshot 9it cannot be edited;.0ach time we run query& we get latest information in the dynaset. Access either displays the dynaset or snapshot for us to iew or perform an action on it& such as deleting or updating.

CHAPTER #
TYPE OF TESTING: <LOC3 / 4HITE <O= TESTING: Black Box Testing -lack -o! Testing is testing the software without any knowledge of the inner workings& structure or language of the module being tested. -lack bo! tests& as most other kinds of tests& must be written from a definiti e 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 bo! .you cannot Hsee, into it. The test pro ides inputs and responds to outputs without considering how the software works. White Box Testing (hite -o! 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 bo! le el. 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 'ield testing will be performed manually and functional tests will be written in detail.

Te&t oDject)@e& All field entries must work properly. Pages must be acti ated from the identified link. The entry screen& messages and responses must not be delayed.

Fe.t;re& to De te&te? @erify that the entries are of the correct format +o duplicate entries should be allowed

All links should take the user to the correct page. SYSTE% TESTING: The purpose of testing is to disco er errors. Testing is the process of trying to disco er e ery concei able fault or weakness in a work product. It pro ides a way to check the functionality of components& sub assemblies& assemblies and=or a finished product It is the process of e!ercising software with the intent of ensuring that the Software system meets its requirements and user e!pectations and does not fail in an unacceptable manner. There are arious types of test. 0ach test type addresses a specific testing requirement. 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 O one step up O software applications at the company le el O interact without error. Te&t Re&;*t&: All the test cases mentioned abo e passed successfully. +o defects encountered.

CHAPTER #E CONCLUSION:
In this paper we ha e worked to facilitate the client in getting a proof of integrity of the data which he wishes to store in the cloud storage ser ers with bare minimum costs and efforts. .ur scheme was de eloped to reduce the computational and storage o erhead of the client as well as to minimi<e the computational o erhead of the cloud storage ser er. (e also minimi<ed the si<e of the proof of data integrity so as to reduce the network bandwidth consumption. $any of the schemes proposed earlier require the archi e to perform tasks that need a lot of computational power to generate the proof of data integrity. -ut in our scheme the archi e "ust need to fetch and send few bits of data to the client.

LI%ITATIONS / FUTURE ENHANCE%ENTS :

Apart from reduction in storage costs data outsourcing to the cloud also

helps in reducing the maintenance. A oiding local storage of data. -y reducing the costs of storage& maintenance and personnel. It reduces the chance of losing data by hardware failures. +ot cheating the owner.

REFERENCE / <I<LIOGRAPHY:

1ood Teachers are worth more than thousand books& we ha e them in .ur Department Re-ere,ce& %.?e Fro9: 4. -eginning ASP.+0T 72 in %C and @- by Imar Spaanjaars. 5. ASP.+0T 7 Unleashed by Stephen alther.

N. Programming ASP.+0T N.A !y "esse #i!erty, Dan $aharry, Dan Hur%it&. 7. -eginning ASP.+0T N.A in %C 566P2 'rom +o ice to Professional& Second 0dition by $atthe% $a'Donald. A. 3. K. P. Ama<on (eb Ser ices 9A(S;& .nline at http2==aws. ama<on.com. 1oogle App 0ngine& .nline at http2==code.google.com=appengine=. $icrosoft A<ure& http2==www.microsoft.com=a<ure=. A. Agrawal et al. (s)bpel e!tension for people 9bpel7people;& ersion 4.6.& 566K. I. $. Amend et al. (eb ser ices human task 9ws)humantask;& ersion 4.6.& 566K. S)te& Re-erre?: http2==www.asp.net.com http2==www.dotnetspider.com= http2==www.dotnetspark.com ADDre@).t)o,&: POR CLS Proo- o- retr)e@.D)*)t8 Co99o, L.,g;.ge S:ec)-)c.t)o,

PDA

Per&o,.* D)g)t.* A&&)&t

SOURCE CODE
using using using using using using using using using using using System; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.Web arts; System.!ml.Linq;

"ublic "artial class #Default $ System.Web.UI. age % "rotecte& 'oi& age#Loa&(ob)ect sen&er* E'ent+rgs e, % "rotecte& 'oi& .utton/#Clic0(ob)ect sen&er* E'ent+rgs % Res"onse.Re&irect(1+&minLogin.as"21,; "rotecte& 'oi& .utton3#Clic0(ob)ect sen&er* E'ent+rgs % Res"onse.Re&irect(1O4nerLogin.as"21,; "rotecte& 'oi& .utton5#Clic0(ob)ect sen&er* E'ent+rgs % Res"onse.Re&irect(1O4nerRegistration.as"21,; "rotecte& 'oi& .utton6#Clic0(ob)ect sen&er* E'ent+rgs % Res"onse.Re&irect(1t"alogin.as"21,; using using using using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.Web arts; System.!ml.Linq; System.Data.SqlClient; e,

e,

e,

e,

"ublic "artial class O4ner7ileDetails $ System.Web.UI. age

SqlConnection con 8 ne4 SqlConnection(Configuration9anager.+""Settings:1ConnectionString1;,; "rotecte& 'oi& age#Loa&(ob)ect sen&er* E'ent+rgs e, % con.O"en(,; if (<Is ost.ac0, % SqlData+&a"ter a&" 8 ne4 SqlData+&a"ter(1Select &istinct fe2t from filearc=i'e 4=ere fo4ner8>1 ? (string,Session:1o4neri&1; ? 1>1* con,; DataSet &s 8 ne4 DataSet(,; a&".7ill(&s,; for (int i 8 @; i A &s.Bables:@;.Ro4s.Count; i??, % Dro"Do4nList/.Items.+&&(&s.Bables:@;.Ro4s:i; :1fe2t1;.BoString(,,; SqlData+&a"ter a&"/ 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e 4=ere fo4ner8>1 ? (string,Session:1o4neri&1; ? 1>1* con,; DataSet &s/8 ne4 DataSet(,; a&"/.7ill(&s/,; Dri&Eie4/.DataSource 8 &s/; Dri&Eie4/.Data.in&(,; ? 1,1,; "rotecte& 'oi& Dro"Do4nList/#Selecte&In&e2C=ange&(ob)ect sen&er* E'ent+rgs e, % if (Dro"Do4nList/.Selecte&Item.Be2t 88 1+ll1, % SqlData+&a"ter a&"/ 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e 4=ere fo4ner8>1 ? (string,Session:1o4neri&1; ? 1>1* con,; DataSet &s/ 8 ne4 DataSet(,; a&"/.7ill(&s/,; Dri&Eie4/.DataSource 8 &s/; Dri&Eie4/.Data.in&(,; else % SqlData+&a"ter a&" 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e 4=ere fe2t8>1 ? Dro"Do4nList/.Selecte&Item.Be2t ? 1> an& fo4ner8>1 ? (string,Session:1o4neri&1; ? 1>1* con,; DataSet &s 8 ne4 DataSet(,; a&".7ill(&s,; Dri&Eie4/.DataSource 8 &s; Dri&Eie4/.Data.in&(,; Label3@.Be2t 8 Con'ert.BoString(1(1 ? &s/.Bables:@;.Ro4s.Count con.Close(,;

"rotecte& 'oi& Dri&Eie4/# ageIn&e2C=anging(ob)ect sen&er* Dri&Eie4 ageE'ent+rgs e, % Dri&Eie4/. ageIn&e2 8 e.Fe4 ageIn&e2; bin&gri&(,; "ublic 'oi& bin&gri&(, % if (Dro"Do4nList/.Selecte&Item.Be2t 88 1+ll1, % SqlData+&a"ter a&"/ 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e 4=ere fo4ner8>1 ? (string,Session:1o4neri&1; ? 1>1* con,; DataSet &s/ 8 ne4 DataSet(,; a&"/.7ill(&s/,; Dri&Eie4/.DataSource 8 &s/; Dri&Eie4/.Data.in&(,; else % SqlData+&a"ter a&" 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e 4=ere fe2t8>1 ? Dro"Do4nList/.Selecte&Item.Be2t ? 1> an& fo4ner8>1 ? (string,Session:1o4neri&1; ? 1>1* con,; DataSet &s 8 ne4 DataSet(,; a&".7ill(&s,; Dri&Eie4/.DataSource 8 &s; Dri&Eie4/.Data.in&(,; using using using using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.Web arts; System.!ml.Linq; System.Data.SqlClient;

"ublic "artial class O4ner7ilesEie4 $ System.Web.UI. age % SqlConnection con 8 ne4 SqlConnection(Configuration9anager.+""Settings:1ConnectionString1;,; string filei&* strmeta&ata; string enc0ey* enc0ey/; Cry"togra"=y cs 8 ne4 Cry"togra"=y(,; "rotecte& 'oi& age#Loa&(ob)ect sen&er* E'ent+rgs e, % filei& 8 Request. arams:1ID1;;

SqlData+&a"ter a&" 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e 4=ere fi&8>1 ? filei& ? 1>1* con,; DataSet &s 8 ne4 DataSet(,; a&".7ill(&s,; Label6.Be2t 8 &s.Bables:@;.Ro4s:@;:1fi&1;.BoString(,; LabelG.Be2t 8 &s.Bables:@;.Ro4s:@;:1ffilename1;.BoString(,; Label/@.Be2t 8 &s.Bables:@;.Ro4s:@;:1fsub)ect1;.BoString(,; Label/5.Be2t 8 &s.Bables:@;.Ro4s:@;:1fe2t1;.BoString(,; Label/H.Be2t 8 &s.Bables:@;.Ro4s:@;:1fsiIein0b1;.BoString(,; Label/J.Be2t 8 &s.Bables:@;.Ro4s:@;:1f&atetime1;.BoString(,; Label35.Be2t 8 &s.Bables:@;.Ro4s:@;:1f'erify1;.BoString(,; strmeta&ata 8 &s.Bables:@;.Ro4s:@;:1fmeta&ata1;.BoString(,; if (strmeta&ata.Lengt= K 6@, % Label3H.Be2t 8 strmeta&ata.Substring(@* 6@, ? 1..1; else % Label3H.Be2t 8 strmeta&ata; Label3J.Be2t 8 &s.Bables:@;.Ro4s:@;:10eyrequest1;.BoString(,; Session:10ey1; 8 &s.Bables:@;.Ro4s:@; :1fenccry"to0ey1;.BoString(,; enc0ey 8 (string,Session:10ey1;; Session:10ey/1; 8 cs.Decry"t(enc0ey,; Session:1"at=1; 8 &s.Bables:@;.Ro4s:@;:1file"at=1;.BoString(,; "rotecte& 'oi& .utton3#Clic0(ob)ect sen&er* E'ent+rgs e, % Res"onse.Re&irect(1O4ner7ileDetails.as"21,; "rotecte& 'oi& Lin0.utton/#Clic0(ob)ect sen&er* E'ent+rgs e, % Res"onse.Re&irect(1O4ner7ileDetails.as"21,; "rotecte& 'oi& Image.utton3#Clic0(ob)ect sen&er* ImageClic0E'ent+rgs e, % age#Loa&(null* E'ent+rgs.Em"ty,; "rotecte& 'oi& btnc=ec0#Clic0(ob)ect sen&er* E'ent+rgs e, % 9o&al o"u"E2ten&er/.S=o4(,; enc0ey/ 8 (string,Session:10ey1;; if (Be2t.o23.Be2t 88 enc0ey/, % Be2t.o25.Be2t 8 (string,Session:10ey/1;; Be2t.o23.Enable& 8 false; btn&o4nloa&.Enable& 8 true; else % string myStringEariable/ 8 string.Em"ty; myStringEariable/ 8 1Cry"togra"=ic Ley Error.1; ClientScri"t.RegisterStartu"Scri"t(t=is.DetBy"e(,* 1myalert1* 1alert(>1 ? myStringEariable/ ? 1>,;1* true,;

"rotecte& 'oi& Lin0.utton3#Clic0(ob)ect sen&er* E'ent+rgs e, % 9o&al o"u"E2ten&er/.S=o4(,; Be2t.o23.Be2t 8 (string,Session:10ey1;; "rotecte& 'oi& btn&o4nloa&#Clic0(ob)ect sen&er* E'ent+rgs e, % anel5.Eisible 8 false; SqlComman& cm& 8 ne4 SqlComman&(1select C from filearc=i'e 4=ere fi& 8 >1 ? Label6.Be2t ? 1>1* con,; DataBable &t 8 DetData(cm&,; if (&t <8 null, % &o4nloa&(&t,; "ri'ate DataBable DetData(SqlComman& cm&, % DataBable &t 8 ne4 DataBable(,; SqlConnection con 8 ne4 SqlConnection(Configuration9anager.+""Settings:1ConnectionString1;,; SqlData+&a"ter s&a 8 ne4 SqlData+&a"ter(,; cm&.Comman&By"e 8 Comman&By"e.Be2t; cm&.Connection 8 con; try % con.O"en(,; s&a.SelectComman& 8 cm&; s&a.7ill(&t,; return &t; catc= % return null; finally % con.Close(,; s&a.Dis"ose(,; con.Dis"ose(,; -

"ri'ate 'oi& &o4nloa&(DataBable &t, % .yte:; bytes 8 (.yte:;,&t.Ro4s:@;:1filebytes1;; Res"onse..uffer 8 true; Res"onse.C=arset 8 11; Res"onse.Cac=e.SetCac=eability(Htt"Cac=eability.FoCac=e,; MMfty"e 8 &t.Ro4s:@;:1filety"e1;.BoString(,;

MMRes"onse.ContentBy"e 8 1a""licationM1? fty"e?1 1; Res"onse.ContentBy"e 8 &t.Ro4s:@;:1fe2t1;.BoString(,; Res"onse.+&&Hea&er(1contentN&is"osition1* 1attac=ment;filename81 ? &t.Ro4s:@;:1ffilename1;.BoString(,,; MMRes"onse..inaryWrite(1Ascri"t ty"e8>te2tM)a'ascri"t>K Aembe& src8>bytes> style84i&t=$5@@"2; =eig=t$3@@"2;K AMembe&K AMscri"tK 1,; Res"onse..inaryWrite(bytes,; Res"onse.7lus=(,; Res"onse.En&(,; using using using using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.Web arts; System.!ml.Linq; System.Data.SqlClient;

"ublic "artial class t"a'erify $ System.Web.UI. age % SqlConnection con 8 ne4 SqlConnection(Configuration9anager.+""Settings:1ConnectionString1;,; "rotecte& 'oi& age#Loa&(ob)ect sen&er* E'ent+rgs e, % SqlData+&a"ter a&"/ 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e1* con,; DataSet &s/ 8 ne4 DataSet(,; a&"/.7ill(&s/,; Dri&Eie4/.DataSource 8 &s/; Dri&Eie4/.Data.in&(,; "rotecte& 'oi& Dri&Eie4/# ageIn&e2C=anging(ob)ect sen&er* Dri&Eie4 ageE'ent+rgs e, % Dri&Eie4/. ageIn&e2 8 e.Fe4 ageIn&e2; bin&gri&(,; "ublic 'oi& bin&gri&(, % SqlData+&a"ter a&"/ 8 ne4 SqlData+&a"ter(1Select C from filearc=i'e1* con,; DataSet &s/ 8 ne4 DataSet(,; a&"/.7ill(&s/,; Dri&Eie4/.DataSource 8 &s/; Dri&Eie4/.Data.in&(,; -

using using using using using using using using using using using using

System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.Web arts; System.Web.UI.HtmlControls; System.!ml.Linq;

"ublic "artial class t"amaster $ System.Web.UI.9aster age % string lin0/* lin03* lin05; string seslin0/* seslin03* seslin05; "rotecte& 'oi& age#Loa&(ob)ect sen&er* E'ent+rgs e, % Label5.Be2t 8 1Welcome* 1 ? 1Onbs"Onbs"1 ? Session:1t"a1; ? 1 <1; Lin0.utton/..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P.6@6@61,; seslin0/ 8 (string,Session:1t"alin0/1;; seslin03 8 (string,Session:1t"alin031;; seslin05 8 (string,Session:1t"alin051;; if (seslin0/ <8 null, % Lin0.utton/..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P.6@6@61,; Lin0.utton3..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; Lin0.utton5..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; Lin0.utton6..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; if (seslin03 <8 null, % Lin0.utton/..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; Lin0.utton3..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P.6@6@61,; Lin0.utton5..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; Lin0.utton6..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; if (seslin05 <8 null,

Lin0.utton/..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; Lin0.utton3..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; Lin0.utton5..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P.6@6@61,; Lin0.utton6..ac0Color 8 System.Dra4ing.ColorBranslator.7romHtml(1P7E3E3E1,; -

"rotecte& 'oi& Lin0.utton/#Clic0(ob)ect sen&er* E'ent+rgs e, % lin0/ 8 1yes1; Session:1t"alin0/1; 8 lin0/; Session.Remo'e(1t"alin031,; Session.Remo'e(1t"alin051,; Res"onse.Re&irect(1t"amain.as"21,; "rotecte& 'oi& Lin0.utton3#Clic0(ob)ect sen&er* E'ent+rgs e, % lin03 8 1yes1; Session:1t"alin031; 8 lin03; Session.Remo'e(1t"alin0/1,; Session.Remo'e(1t"alin051,; Res"onse.Re&irect(1t"a'erify.as"21,; "rotecte& 'oi& Lin0.utton5#Clic0(ob)ect sen&er* E'ent+rgs e, % lin05 8 1yes1; Session:1t"alin051; 8 lin05; Session.Remo'e(1t"alin0/1,; Session.Remo'e(1t"alin031,; Res"onse.Re&irect(1t"afile&etails.as"21,; "rotecte& 'oi& Lin0.utton6#Clic0(ob)ect sen&er* E'ent+rgs e, % Session.Remo'e(1t"alin0/1,; Session.Remo'e(1t"alin031,; Session.Remo'e(1t"alin051,; Res"onse.Re&irect(1Default.as"21,; -