0000083: AuthServer has its own SHA512 for some reason; use 3rdparty/cryptopp instead.

ID	Project	Category	View Status	Date Submitted	Last Update

0000083	Volume 2	Task	public	2019-05-13 10:29	2019-07-26 10:19

Reporter	Taffer	Assigned To	Cattan
Priority	normal	Severity	minor	Reproducibility	always
Status	assigned	Resolution	open
Product Version	Issue 1
Target Version	Issue 2	Fixed in Version

Summary	0000083: AuthServer has its own SHA512 for some reason; use 3rdparty/cryptopp instead.
Description	AuthServer/lib/cryptLib is a SHA512 implementation. Instead of rolling their own, AuthServer should just use SHA512 from Crypto++ in 3rdparty/cryptopp... it's probably already got cryptopp as a dependency, most of the projects link against it.
Steps To Reproduce	Look in AuthServer/lib/cryptLib and have a WTF moment.
Tags	No tags attached.

subsystem

Date Modified	Username	Field	Change
2019-05-13 10:29	Taffer	New Issue
2019-05-13 10:32	Taffer	Note Added: 0000056
2019-07-26 10:19	Cattan	Assigned To	=> Cattan
2019-07-26 10:19	Cattan	Status	new => assigned

Taffer 2019-05-13 10:32 developer ~0000056	This will require some testing to ensure nothing is depending on any bugs that might be present in AuthServer's SHA512 implementation vs. the one in Crypto++. I'm assuming you only hit AuthServer when you first log in, so maybe I'm underestimating the test step.