2012/7/31 Ozkan Sezer <[email protected]>: > On 7/31/12, Kai Tietz <[email protected]> wrote: >> Hi Ozkan, > [...] >> So, to avoid such issues in future I begun to abstract secure-API in >> our runtime. See revision 5290 as a start. Important here is that >> for msvcrt.dll we have to remove the secured-API > > Was marking the msvcrt.dll exports as DATA not our policy > in these kinds of situations? > >> and remove the >> _CRTIMP from the header-definition, as soon as we have a forwarder >> (and or emulation) function in secapi/ folder. >> >> Regards, >> Kai > > -- > O.S.
Well, not in this case. We mark it as DATA, if we are overriding functionality, but we can be sure that import is present. Here we have to deal with the issue that import-function might not be present in msvcrt, so we need to remove it from msvcrt's import library and deal with the _imp-symbol ourself. Kai ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
