Microsoft http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png http://channel9.msdn.com/Tags/louis+lafreniere Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Tags/louis+lafreniere en Wed, 19 Jun 2013 03:15:38 GMT Wed, 19 Jun 2013 03:15:38 GMT Rev9 3 1 25 the C++ Team Blog: A lot of code written in C and C++ has vulnerabilities that leave their users open to buffer overrun attacks. There are two major reasons for this. One reason is that the languages provide unfettered access to the vulnerable memory; the other reason is that developers make mistakes. The simple fact is that even following the best practices and performing quality checks, by the end of the day, no developers can get 100 percent of their code right all the time. Thus, additional built-in layers of defense to help track down vulnerable areas of code are in order. The Visual C++ compiler’s GS switch, which is on by default, is one of the built-in defenses designed to mitigate the buffer overrun attacks.

With VC 10, the next iteration of VC that ships with Visual Studio 2010, Louis Lafreniere and team have delivered the next iteration of /GS, /GS++. /GS proved to be invaluable for C++ developers wanting compile time checking for buffer overrun vulnerabilities in their code. specifically targetting string buffers. Well, turns out that certain structs proved to be a suitable exploit and /GS did not check data structures like structs. Louis et al, with /GS++, now check for certain typed of struct vulnerability (stack allocated).

Here, Principal Developer Louis Lafreniere takes us through the history and future of /GS, in a deep way, of course. Most of the time is spent at the whiteboard mapping out exactly how /GS works and what to expect from /GS++.

Enjoy! ]]> http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-Next-Generation-Buffer-Overrun-Protection-gs From the C++ Team Blog: A lot of code written in C and C++ has vulnerabilities that leave their users open to buffer overrun attacks. There are two major reasons for this. One reason is that the languages provide unfettered access to the vulnerable memory; the other reason is that developers make mistakes. The simple fact is that even following the best practices and performing quality checks, by the end of the day, no developers can get 100 percent of their code right all the time. Thus, additional built-in layers of defense to help track down vulnerable areas of code are in order. The Visual C++ compiler’s GS switch, which is on by default, is one of the built-in defenses designed to mitigate the buffer overrun attacks. With VC 10, the next iteration of VC that ships with Visual Studio 2010, Louis Lafreniere and team have delivered the next iteration of /GS, /GS++. /GS proved to be invaluable for C++ developers wanting compile time checking for buffer overrun vulnerabilities in their code. specifically targetting string buffers. Well, turns out that certain structs proved to be a suitable exploit and /GS did not check data structures like structs. Louis et al, with /GS++, now check for certain typed of struct vulnerability (stack allocated). Here, Principal Developer Louis Lafreniere takes us through the history and future of /GS, in a deep way, of course. Most of the time is spent at the whiteboard mapping out exactly how /GS works and what to expect from /GS++. Enjoy! 1919 http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-Next-Generation-Buffer-Overrun-Protection-gs Tue, 02 Jun 2009 16:34:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-Next-Generation-Buffer-Overrun-Protection-gs Charles Charles 9 http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-Next-Generation-Buffer-Overrun-Protection-gs/RSS C++ Compilers Louis Lafreniere Programming Security
What is a structured exception, exactly? How should you handle exceptions that you don't assume will arise during the execution of your code? What are the correct patterns of exception handling that you can safely rely on? What does the C++ compiler have to do with exception code patterns?

Come along for ride into the deep and murky world of exceptions with some folks that truly understand them at the most fundamental levels.

Ale Contenti is a senior development lead in the C++ base class libraries team. Louis Lafreniere is a principal software developer in the C++ compiler group. Here, Ale and Louis teach us about exceptions and handling them (and when not to handle them). I love talking to the VC++ People. They live on the metal and really understand the fascinating intracacies of our platform.

Enjoy this latest Going Deep episode. ]]> http://channel9.msdn.com/Shows/Going+Deep/Ale-Contenti-and-Louis-Lafreniere-Understanding-Exceptions-and-WhenHow-to-Handle-Them Sometimes, things go wrong when code executes. You can't predict when this will happen or even why, but you can write code to handle exceptional problems. If you're lucky, the problem will carry with it a bunch of useful information that you can use, at runtime, to handle the specific error. These exceptional information structures are called structured exceptions; blobs of bad news carrying useful and specific information that you can use to find your way out of the exceptional rabbit hole. Of course, with useful data packaged up in an exception you can more easily debug to find root causes, which is much harder to do with, say, error codes...What is a structured exception, exactly? How should you handle exceptions that you don't assume will arise during the execution of your code? What are the correct patterns of exception handling that you can safely rely on? What does the C++ compiler have to do with exception code patterns? Come along for ride into the deep and murky world of exceptions with some folks that truly understand them at the most fundamental levels.Ale Contenti is a senior development lead in the C++ base class libraries team. Louis Lafreniere is a principal software developer in the C++ compiler group. Here, Ale and Louis teach us about exceptions and handling them (and when not to handle them). I love talking to the VC++ People. They live on the metal and really understand the fascinating intracacies of our platform.Enjoy this latest Going Deep episode. 3336 http://channel9.msdn.com/Shows/Going+Deep/Ale-Contenti-and-Louis-Lafreniere-Understanding-Exceptions-and-WhenHow-to-Handle-Them Fri, 21 Sep 2007 00:47:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Ale-Contenti-and-Louis-Lafreniere-Understanding-Exceptions-and-WhenHow-to-Handle-Them Charles Charles 17 http://channel9.msdn.com/Shows/Going+Deep/Ale-Contenti-and-Louis-Lafreniere-Understanding-Exceptions-and-WhenHow-to-Handle-Them/RSS Ale Contenti C++ Compilers Computing Exceptions Louis Lafreniere Programming long time; 15 years, to be exact. Specifically, Louis works on the backend compiler. What's a backend compiler? How's it evolved over the years? Where's it going? Watch and listen. Good stuff. ]]> http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-VC-backend-compiler Louis Lafreniere has been a developer on the VC++ compiler team for a long time; 15 years, to be exact. Specifically, Louis works on the backend compiler. What's a backend compiler? How's it evolved over the years? Where's it going? Watch and listen. Good stuff. http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-VC-backend-compiler Thu, 11 May 2006 20:24:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-VC-backend-compiler Charles Charles 13 http://channel9.msdn.com/Shows/Going+Deep/Louis-Lafreniere-VC-backend-compiler/RSS C++ Louis Lafreniere WiX