Hugo Trippaers bd58ceccd8 Summary: Make the authenticator responsible for encoding the password and add a SHA256 salted authenticator ... The authenticators now have an encode function that cloudstack will use to encode the user supplied password before storing it in the database. This makes it easier to add other authenticators with other hashing algorithms. The requires a two step approach to creating the admin account at first start as the authenticators are only present in the management-server component locator. The SHA256 salted authenticator make use of this new system and adds a hashing algorithm based on SHA256 with a salt. This type of hash is far less susceptible to rainbow table attacks. To make use of these new features the users password will be sent over the wire just as he typed it and it will be transformed into a hash on the server and compared with the stored password. This means that the hash will not go over the wire anymore. The default authenticator in components.xml is still set to md5 for backwards compatibility. For new installations the sha256 could be enabled.		2012-10-30 12:56:56 +01:00
..
deployment-planners	Updated master to 4.1.0	2012-10-01 11:00:55 -07:00
file-systems/netapp	Check manageontap sdk version and provide instructions.	2012-10-15 17:25:40 +02:00
host-allocators/random	Updated master to 4.1.0	2012-10-01 11:00:55 -07:00
hypervisors	Summary: Allow public and private nic to be the same bridge	2012-10-29 23:13:26 -06:00
network-elements	The interface change introduced by commit	2012-10-18 09:40:13 +02:00
storage-allocators/random	Updated master to 4.1.0	2012-10-01 11:00:55 -07:00
user-authenticators	Summary: Make the authenticator responsible for encoding the password and add a SHA256 salted authenticator	2012-10-30 12:56:56 +01:00
pom.xml	Summary: Make the authenticator responsible for encoding the password and add a SHA256 salted authenticator	2012-10-30 12:56:56 +01:00