Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Scott Currie - How is Visual C++ (Whidbey) going to make my code more secure?

Download

Right click “Save as…”

Developers are being asked to create more secure code. The next version of Visual C++, code-named Whidbey, will introduce several new security-protection capabilities. Here Scott Currie, Scott Currie, program manager of Visual C++ discusses the new security-focused changes.

Tags:

Follow the Discussion

  • Sven GrootSven Groot Don't worry... I'm a doctor.
    Sounds interesting. You'll defenitely need to get those secure C APIs standardised though, everybody from Linux to MacOS could benefit from that kind of thing. Not that they'd trust it if it comes from Microsoft, but still...
    Also, real C++ programmers don't use C APIs anyway, I mean, who needs scanf and char* when you've got std::cin and std::string (both of which are safe btw)? Wink

    Also, it's not exactly clear to me what's so new about this stack buffer overrun protection... VS.NET 2003 does that too. Sure, I assume you've optimised it more, but is there anything really completely totally new added to it? That didn't become very clear from the video to me.
  • b0bb0b
    Hmm. Looks like this is a good idea for me to use. My programs use a lot of buffers. This will fix a lot of peoples code that would just crash because they didn't use malloc().

    Good idea.
  • AcidHelmNunAcidHelmNun Would you like fries with that?
    Don't dis the C APIs entirely, I use printf and sprintf all the time (and indirectly via CString::Format). Creating formatted output with them is SO much easier compared to using the stream classes and manipulators and the horribly-named functions that I have to look up every single time.
  • Sven GrootSven Groot Don't worry... I'm a doctor.
    Easier, perhaps. Less readable and more error-prone, definitely.

    It's probably a matter of taste, but I prefer the C++ way whenever there is one anyway.
  • It'll be cool if you could give us more samples.Thank you.
  • I'm just curious, have the STL functions that take 2 iterators (begin and end) for the input container and 1 for the optput been reworked too? So that they take also an iterator to the end of the output?

    I'm thinking of algorithms like copy or transform.

Remove this comment

Remove this thread

close

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.