Details
-
Type:
Improvement
-
Status:
In Progress
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 1.0 B1
-
Fix Version/s: None
-
Component/s: Build, Infrastructure and Tests
-
Labels:None
-
keywords:security cookies
-
Development Priority:Medium
-
Similar issues:
XWIKI-5863 Switch to cookie encryption using a cipher provided by bouncycastle. XWIKI-2259Configurable prefix for authentication cookies XWIKI-1655login action should clean all the cookies XWIKI-5156Session cookies are not marked as HttpOnly XWIKI-2463Login cookie validation hash mismatch with Tomcat 5.5.20-2etch2 XWIKI-2211Cannot log in using Internet Explorer XWIKI-2206Cookie domains not compliant with RFC 2109 XWIKI-8909 Random Infinispan error on WebSphere
Description
xwiki.cfg has two parameters, xwiki.authentication.validationKey and xwiki.authentication.encryptionKey, responsible for cookie encryption. These two have predefined values which can be used by an attacker to decode the username/password.
It would be better if the installer (.exe, ant or maven) would generate:
1. a random key pair
2. a host-dependent key-pair, different for each host, but always the same for a host
For the moment this should be documented in the release notes that admins should change them.