warning C4477: 'printf' : format string '%ws' requires an argument of type 'wchar_t *', but variadic argument 1 has type 'LPBYTE'
sec13b opened this issue · 2 comments
Build started...
1>------ Build started: Project: DeobfuscateSecretString, Configuration: Debug x64 ------
2>------ Build started: Project: SharpSCCM, Configuration: Debug x64 ------
1>DeobfuscateSecretString.cpp
2> SharpSCCM -> C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\bin\x64\Debug\SharpSCCM.exe
1>C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\DeobfuscateSecretString.cpp(26,15): warning C4200: nonstandard extension used: zero-sized array in struct/union
1>C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\DeobfuscateSecretString.cpp(26,15): message : This member will be ignored by a defaulted constructor or copy/move assignment operator
1>C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\DeobfuscateSecretString.cpp(92,24): warning C4477: 'printf' : format string '%ws' requires an argument of type 'wchar_t *', but variadic argument 1 has type 'LPBYTE'
1>C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\DeobfuscateSecretString.cpp(92,24): message : consider using '%hs' in the format string
1>C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\DeobfuscateSecretString.cpp(92,24): message : consider using '%s' in the format string
1>C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\DeobfuscateSecretString.cpp(92,24): message : consider using '%Ts' in the format string
1>DeobfuscateSecretString.vcxproj -> C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\DeobfuscateSecretString\x64\Debug\DeobfuscateSecretString.exe
1>Done building project "DeobfuscateSecretString.vcxproj".
3>------ Build started: Project: UnitTests, Configuration: Debug x64 ------
3> UnitTests -> C:\Users\Asus\Desktop\cobaltkits\SharpSCCM\UnitTests\bin\x64\Debug\SharpSCCM.UnitTests.dll
========== Build: 3 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Elapsed 00:06.652 ==========
@sec13b it looks like the build succeeded. Could you please provide some more context for this issue? If it is related to the warnings, I'm haven't worried about it since the build succeeds and the executable successfully decrypts secrets, but if there's something else that should to be fixed or a good reason I should try and get rid of those warnings I'd be happy to take a closer look.
Closing this issue due to inactivity.