Manage (generate/read) Salt within Authorization class

[GoogleCodeExporter]

The salt is currently generated outside the Authorization class. This means we 
have a global assumption (that some salt is generated). We should better put 
salt-management inside the class to decouple it (the rest of phpLiteAdmin 
doesn't use the salt).

(This issue has first been mentioned as a comment in issue #170.)

Original issue reported on code.google.com by crazy4ch...@gmail.com on 9 Feb 2013 at 9:28

[GoogleCodeExporter]

Agreed. We can also remove the SYSTEMPASSWORDENCRYPTED constant and make it a 
[static] property of Authorization.

Original comment by dreadnaut on 10 Feb 2013 at 2:12

• Changed state: Accepted
• Added labels: Maintainability

[GoogleCodeExporter]

yes, good idea.

Original comment by crazy4ch...@gmail.com on 10 Feb 2013 at 3:52

[GoogleCodeExporter]

Here's a patch against r333. It moves the hash generation in Authorization's 
constructor and replaces SYSTEMPASSWORDENCRYPTED with 
->system_password_encrypted.

Original comment by dreadnaut on 10 Feb 2013 at 7:08

Attachments:

• hash-in-auth-r333.diff

[GoogleCodeExporter]

Thanks. Looks good. Please commit it to svn.

Original comment by crazy4ch...@gmail.com on 15 Feb 2013 at 2:41

[GoogleCodeExporter]

This issue was closed by revision r338.

Original comment by dreadnaut on 15 Feb 2013 at 10:57

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, committed as r338.

Original comment by dreadnaut on 15 Feb 2013 at 10:58