Commit Graph

21 Commits

Author SHA1 Message Date
Abhinandan Prateek
e65dbbc3cf Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 1b2b58fe35.
2013-12-16 15:42:51 +05:30
Abhinandan Prateek
1b2b58fe35 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-16 15:36:37 +05:30
Abhinandan Prateek
2bdd288605 Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit cc662445a5.
2013-12-13 11:53:40 +05:30
Abhinandan Prateek
cc662445a5 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-13 11:46:08 +05:30
Abhinandan Prateek
3c561c6d79 Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 6ba071b159.
2013-12-03 17:46:18 +05:30
Abhinandan Prateek
6ba071b159 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-03 17:41:35 +05:30
Abhinandan Prateek
92254a5a2f Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 7fb9dcb131e1d2d5a7c87e0aab2929b772bcd008.
2013-12-03 17:16:18 +05:30
Abhinandan Prateek
e8c3c650a7 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-03 17:16:17 +05:30
Abhinandan Prateek
4cb311530c Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 0b9eadaf14.
2013-11-12 21:17:27 +05:30
Abhinandan Prateek
0b9eadaf14 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-11-12 21:15:01 +05:30
animesh
21043bfe84 Updating pom.xml version numbers for release 4.2.1-SNAPSHOT
Signed-off-by: animesh <animesh@apache.org>
2013-10-03 17:13:17 -07:00
Animesh Chaturvedi
06f28722b6 Updating pom.xml version numbers for release 4.2.0
Signed-off-by: Animesh Chaturvedi <animesh@Animesh-LinuxDev.citrite.net>
2013-08-22 17:15:42 -07:00
Alex Huang
cea7363bde Fixed a compile error caused by eclipse 2013-08-07 19:52:53 -07:00
Alex Huang
7ec469f081 Disabled the authenticator test. It doesn't always pass due to timing issues 2013-08-07 17:01:06 -07:00
Amogh Vasekar
c917e3884b CLOUDSTACK-2312, CLOUDSTACK-2314 : SHA256 timing attack and brute force attack fix
Signed-off-by: Chiradeep Vittal <chiradeep@apache.org>
2013-08-07 12:18:10 -07:00
Vijayendra Bhamidipati
2dbdc46337 CLOUDSTACK-1734: Make SHA1 default password encoding mechanism
Description:

	Making SHA256SALT the default encoding algorithm to encode
	passwords when creating/updating users.

	Introducing a new configurable list to allow admins to
	separately configure the order of preference for encoding
	and authentication schemes.

	Since passwords are now sent by clients as clear text,
	fixing the Plain text authenticator to check against the
	password passed in rather than its md5 digest.
2013-04-02 17:40:50 -07:00
Rohit Yadav
80d58b6c73 CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
2013-02-20 16:42:56 +05:30
Alex Huang
fac2270240 more files changed 2013-01-10 15:29:14 -08:00
Alex Huang
56e5fbdee2 removed import of componentlocator and inject from all files 2013-01-10 11:44:47 -08:00
Chip Childers
713418c0aa Fixed license headers in 2 files
Signed-off-by: Chip Childers <chip.childers@gmail.com>
2012-10-31 14:29:38 -04:00
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