You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by mg...@apache.org on 2014/11/17 09:22:04 UTC

svn commit: r1640091 - /wicket/common/site/trunk/_site/guide/guide/src/docs/guide/security/security_4.gdoc

Author: mgrigorov
Date: Mon Nov 17 08:22:03 2014
New Revision: 1640091

URL: http://svn.apache.org/r1640091
Log:
Fix typos and add links to prevent broken state.


Modified:
    wicket/common/site/trunk/_site/guide/guide/src/docs/guide/security/security_4.gdoc

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/security/security_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/security/security_4.gdoc?rev=1640091&r1=1640090&r2=1640091&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/security/security_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/security/security_4.gdoc Mon Nov 17 08:22:03 2014
@@ -1,4 +1,4 @@
-In chapter 10.6 we have seen how to use encryted URLs using mapper @CryotoMapper@. To encrypt/decryp page URLs @CryotoMapper@ uses an instance of interface @org.apache.wicket.util.crypt.ICrypt@:
+In chapter [10.6|guide:urls_6] we have seen how to use encryted URLs using mapper @CryptoMapper@. To encrypt/decrypt page URLs @CryptoMapper@ uses an instance of interface @org.apache.wicket.util.crypt.ICrypt@:
 
 {code}
 public interface ICrypt
@@ -9,7 +9,7 @@ public interface ICrypt
 }
 {code}
 
-The default implementation for this interface is class @org.apache.wicket.util.crypt.SunJceCrypt@ which provides password-based cryptography and is adopted by @CryotoMapper@ when we use its constructor @CryptoMapper(IRequestMapper wrappedMapper, Application application)@. As we hinted at the end of chapter 10.6, this constructor alone might not provide enough security for our application. To strengthen the cryptography mechanism used by @CryotoMapper@ we have two possible options.
+The default implementation for this interface is class @org.apache.wicket.util.crypt.SunJceCrypt@ which provides password-based cryptography and is adopted by @CryptoMapper@ when we use its constructor @CryptoMapper(IRequestMapper wrappedMapper, Application application)@. As we hinted at the end of chapter [10.6|guide:urls_6], this constructor alone might not provide enough security for our application. To strengthen the cryptography mechanism used by @CryptoMapper@ we have two possible options.
 The first (and more obvious) is to use constructor @CryptoMapper(IRequestMapper wrappedMapper, IProvider<ICrypt> cryptProvider)@ and give it an implementation of @org.apache.wicket.util.IProvider@ that returns a custom @org.apache.wicket.util.crypt.ICrypt@. 
 
 {note}
@@ -31,10 +31,10 @@ The second option we have to strengthen 
 public void init() {
 	super.init();
 	getSecuritySettings().setCryptFactory(new KeyInSessionSunJceCryptFactory());
-        setRootRequestMapper(new CryptoMapper(getRootRequestMapper(), this));
+	setRootRequestMapper(new CryptoMapper(getRootRequestMapper(), this));
 }
 {code}
 
 
-This cipher factory is used by @CryotoMapper@ when we instantiate it with the first contructor we have seen. Chiper factories are implementations of interface @org.apache.wicket.util.crypt.ICryptFactory@.
-Class @org.apache.wicket.core.util.crypt.KeyInSessionSunJceCryptFactory@ is a built-in cipher factory that generates a separate key for each user and stores it in the HTTP session. This factory offers a stronger URLs encryption and can help to protect our application against CSRF attacks   
+This cipher factory is used by @CryptoMapper@ when we instantiate it with the first contructor we have seen. Cipher factories are implementations of interface @org.apache.wicket.util.crypt.ICryptFactory@.
+Class @org.apache.wicket.core.util.crypt.KeyInSessionSunJceCryptFactory@ is a built-in cipher factory that generates a separate key for each user and stores it in the HTTP session. This factory offers a stronger URLs encryption and can help to protect our application against [CSRF|https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)] attacks.