Timeline for Was API hooking done as needed for Stuxnet to work? I don't think so
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2012 at 9:08 | comment | added | The Kaykay | Okay. But we don't know when was WinCC's STL Editor written. So anything is possible. They might have written using only *A versions or they might have used *W versions too. But since by default WinCC supports five languages English, German, Spanish, French and Italian and also has WinCC Asian version for Japanese, Chinese and Korean, can we say that WinCC uses only *A versions of APIs? | |
| Apr 15, 2012 at 5:50 | comment | added | Dean Harding |
Technically it's possible to choose between calling CreateFileW and CreateFileA at runtime, but in practise it never happens. It's far too complicated and since one is just written in terms of the other, there's just no benefit (i.e. if you ever "need" the CreateFileW version, it's easier to just call CreateFileW in all situations). In most situations, the *A versions are almost always used by applications that were originally written before Windows 2000/XP became the dominant versions of Windows (it's harder to convert from *A to *W than to use *W from the start).
|
|
| Apr 14, 2012 at 13:23 | comment | added | The Kaykay |
Yes absolutely it would be dependent on the filename and not the content of the file. And, CreateFileA() internally calls CreateFileW() Be the filename in Unicode or not CreateFileW() would be called anyway. But CreateFileA() would be called is not necessarily true right? But it would all depend on UNICODEwas used in compiling WinCC or not. Is there any possibility that 'locale' configuration would affect which of the two functions will be called by WinCC? Can WinCC be configured in a way to call CreateFileA() in the US and CreateFileW() in Japan or the Middle East?
|
|
| Apr 14, 2012 at 12:24 | history | answered | Dean Harding | CC BY-SA 3.0 |