Partager via


Repel Attacks on Your Code with the Visual Studio 2005 Safe C and C++ Libraries

Martyn Lovell has written a paper about the Safe C and C++ libraries coming in Whidbey.

https://msdn.microsoft.com/msdnmag/issues/05/05/SafeCandC/default.aspx

Comments

  • Anonymous
    April 13, 2005
    The comment has been removed
  • Anonymous
    April 22, 2005
    Does this protect against the potential overflowed integer calculations in the various ranged insert() STL container member functions and make_heap and pop_heap (and any other function that eventually calls an adjust_heap helper function)?
  • Anonymous
    April 27, 2005
    Re: Safe CRT and StrSafe
    The big difference is Safe CRT is going through the standardization process, StrSafe was born 3 years ago in Windows, for use mainly within Windows.

    Re: OpenBSD
    What makes strlcpy (etc.) different/better? They are bounded function calls too...
  • Anonymous
    May 04, 2005
    Michael, thank you for your answer!

    Re:re: OpenBSD

    Sorry, the question arose from my misunderstanding of *_s function semantics (I thought that wcscat_s needs strncat-like counter maintenance). They DO actually have the same semantics as strlcpy and that is great.