ddnet/src/base/hash_openssl.c

#if defined(CONF_OPENSSL)
#include "hash_ctxt.h"

void sha256_init(SHA256_CTX *ctxt)
{
	SHA256_Init(ctxt);
}

void sha256_update(SHA256_CTX *ctxt, const void *data, size_t data_len)
{
	SHA256_Update(ctxt, data, data_len);
}

SHA256_DIGEST sha256_finish(SHA256_CTX *ctxt)
{
	SHA256_DIGEST result;
	SHA256_Final(result.data, ctxt);
	return result;
}
#endif
Use more secure hash function for map downloads SHA256 was chosen because it is reasonably standard, the file names don't explode in length (this rules out SHA512) and it is supported by basically all versions of OpenSSL (this rules out SHA512/256 and SHA3). The protocol is changed in a backward compatible way: The supporting server sends the SHA256 corresponding to the map in the `MAP_DETAILS` message prior to sending the `MAP_CHANGE` message. The client saves the SHA256 obtained from the `MAP_DETAILS` message until the next `MAP_CHANGE` message. For servers not supporting this protocol, the client falls back to simply opening maps like in the previous scheme. Remove the `map_version` tool, it is not being used and would have been a little bit effort to update. Use the OpenSSL implementation of SHA256 if it is supported, otherwise fall back to a public domain one. Fix #1127. 2018-06-05 19:22:40 +00:00			`#if defined(CONF_OPENSSL)`
			`#include "hash_ctxt.h"`

			`void sha256_init(SHA256_CTX *ctxt)`
			`{`
			`SHA256_Init(ctxt);`
			`}`

			`void sha256_update(SHA256_CTX ctxt, const void data, size_t data_len)`
			`{`
			`SHA256_Update(ctxt, data, data_len);`
			`}`

			`SHA256_DIGEST sha256_finish(SHA256_CTX *ctxt)`
			`{`
			`SHA256_DIGEST result;`
			`SHA256_Final(result.data, ctxt);`
			`return result;`
			`}`
			`#endif`