Closed koraa closed 5 years ago
sha512 and the standard ECC used in sauerbraten are shipped alongside openssl. That's why I would suggest rather replacing both cypher's with openssl's suite, because it is commonly accepted, fast, and works.
Also we can use one of the openssl-forks for example libressl, but openssl will be good too (but as far as i know both of them doesn't support tiger-hash)
@N0Wire only the hash of the authkey (kinda like, salt) is generated using tiger. This part can be easily replaced with any string hashing method we would like to use!
Authkeys will be deprecated and so should it's generation be.
@a-teammate didn't your branch deprecate this? Can this ticket be closed?
What is the replacement for authkeys?
OAuth
We shouldn't close this ticket as long as the replacement is not implemented.
This will be deprecated in the new engine. None of the sauer crypto code is used.
Sauer implements at least it's own version of the tiger hash and a public/private-key scheme. Investigate what can be replaced and which external projects to embed.
See for instance: http://www.cryptopp.com/