Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Not-safe function strcpy, possible buffer overflow #901
There  we use strcpy, first arg may contain
Maybe we should strive to use safe C++ string functions everywhere, instead of archaic strcpy/strcat buffer manipulation.
Edit: especially in this case, as the function returns a std::string already.
Edit2: the rest of the function could be simplified too, to simply call SHGetSpecialFolderPathA, as we require _WINNT 0x0501 (Windows XP) and the function was introduced in 5.0 (Windows 2000).