From 29d40192ed3dc0085b5e513ec071c81e03e95d3b Mon Sep 17 00:00:00 2001 From: xue <> Date: Thu, 23 Mar 2006 13:25:09 +0000 Subject: Reorganized quickstart tutorial. --- .../protected/pages/Security/ViewState.page | 26 ---------------------- 1 file changed, 26 deletions(-) delete mode 100644 demos/quickstart/protected/pages/Security/ViewState.page (limited to 'demos/quickstart/protected/pages/Security/ViewState.page') diff --git a/demos/quickstart/protected/pages/Security/ViewState.page b/demos/quickstart/protected/pages/Security/ViewState.page deleted file mode 100644 index 1b79c272..00000000 --- a/demos/quickstart/protected/pages/Security/ViewState.page +++ /dev/null @@ -1,26 +0,0 @@ - - -

Viewstate Protection

-

-Viewstate lies at the heart of PRADO. Viewstate represents data that can be used to restore pages to the state that is last seen by end users before making the current request. By default, PRADO uses hidden fields to store viewstate information. -

-

-It is extremely important to ensure that viewstate is not tampered by end users. Without protection, malicious users may inject harmful code into viewstate and unwanted instructions may be performed when page state is being restored on server side. -

-

-To prevent viewstate from being tampered, PRADO enforces viewstate HMAC (Keyed-Hashing for Message Authentication) check before restoring viewstate. Such a check can detect if the viewstate has been tampered or not by end users. Should the viewstate is modified, PRADO will stop restoring the viewstate and return an error message. -

-

-HMAC check requires a private key that should be secret to end users. Developers can either manually specify a key or let PRADO automatically generate a key. Manually specified key is useful when the application runs on a server farm. To do so, configure TSecurityManager in application configuration, -

- -<modules> - <module id="security" - class="TSecurityManager" - ValidationKey="my private key" /> -</modules> - -

-HMAC check does not prevent end users from reading the viewstate content. An added security measure is to encrypt the viewstate information so that end users cannot decipher it. To enable viewstate encryption, set the EnableStateEncryption of pages to true. This can be done in page configurations or in page code. Note, encrypting viewstate may degrade the application performance. A better strategy is to store viewstate on the server side, rather than the default hidden field. -

-
\ No newline at end of file -- cgit v1.2.3