raze/source/common/thirdparty/base64.h

//
//  base64 encoding and decoding with C++.
//  Version: 1.01.00
//

#ifndef BASE64_H_C0CE2A47_D10E_42C9_A27C_C883944E704A
#define BASE64_H_C0CE2A47_D10E_42C9_A27C_C883944E704A

TArray<uint8_t> base64_encode(unsigned char const* bytes_to_encode, size_t in_len);
void base64_decode(void* memory, size_t len, const char* encoded_string);

#endif /* BASE64_H_C0CE2A47_D10E_42C9_A27C_C883944E704A */
- various fixes and improvements related to file location management: * saving of demos and savegames no longer mindlessly writes to the mod directory. All such access is now being rerouted through the special paths interface so that the game data can reside in write protected locations. * refactored all occurences of klistpath except fnlist_getnames. * do not allow CON scripts to write to arbitrary files. This is a massive exploit and can be used to cause real damage if someone knows how to play this thing - it's far easier than people may think! It will now write any such data to a special section in the main config which is safe and cannot be manipulated to write to random locations on the hard drive. 2019-11-01 23:38:30 +00:00			`//`
			`// base64 encoding and decoding with C++.`
			`// Version: 1.01.00`
			`//`

			`#ifndef BASE64_H_C0CE2A47_D10E_42C9_A27C_C883944E704A`
			`#define BASE64_H_C0CE2A47_D10E_42C9_A27C_C883944E704A`

- implemented the automap serializer. Also optimized the base64 encoder to avoid creating endless memory copies, thanks to using std::string which is a really poor container for this kind of stuff when workig with larger blocks of data. 2020-09-06 11:39:57 +00:00			`TArray<uint8_t> base64_encode(unsigned char const* bytes_to_encode, size_t in_len);`
			`void base64_decode(void* memory, size_t len, const char* encoded_string);`
- various fixes and improvements related to file location management: * saving of demos and savegames no longer mindlessly writes to the mod directory. All such access is now being rerouted through the special paths interface so that the game data can reside in write protected locations. * refactored all occurences of klistpath except fnlist_getnames. * do not allow CON scripts to write to arbitrary files. This is a massive exploit and can be used to cause real damage if someone knows how to play this thing - it's far easier than people may think! It will now write any such data to a special section in the main config which is safe and cannot be manipulated to write to random locations on the hard drive. 2019-11-01 23:38:30 +00:00
			`#endif /* BASE64_H_C0CE2A47_D10E_42C9_A27C_C883944E704A */`