Merge pull request #411 from Microsoft/kraigb-python

Add security warning

Author: ghogen

docs/porting/port-migrate-and-upgrade-visual-studio-projects.md

@@ -63,7 +63,7 @@ The following list describes support in Visual Studio 2017 for projects that wer
 | InstallShield<br/>MSI setup | Installer projects created in Visual Studio 2010 can be opened in later versions with the help of the [Visual Studio Installer Projects extension](https://marketplace.visualstudio.com/items?itemName=UnniRavindranathan-MSFT.MicrosoftVisualStudio2013InstallerProjects), You can also maintain such projects using [InstallShield Limited Edition](https://blogs.msdn.microsoft.com/visualstudio/2013/08/15/whats-new-in-visual-studio-2013-and-installshield-limited-edition/). |
 | LightSwitch | LightSwitch is no longer supported in Visual Studio 2017. Projects created with Visual Studio 2012 and earlier opened in Visual Studio 2013 or Visual Studio 2015 will be upgraded and can be opened only in Visual Studio 2013 or Visual Studio 2015 thereafter. |
 | Microsoft Azure Tools for Visual Studio | To open these types of projects, first install the [Azure SDK for .NET](http://azure.microsoft.com/en-us/downloads/), then open the project. If necessary, your project will be updated. |
-| Model-View-Controller framework (ASP.NET MVC) | Support for MVC versions and Visual Studio:<ul><li>Visual Studio 2010 SP1 supports MVC 2 and MVC 3; MVC 4 support is added through the [ASP.NET 4 MVC 4 for Visual Studio 2010 SP1 download](https://www.microsoft.com/en-us/download/details.aspx?id=30683)</li><li>Visual Studio 2012 supports only MVC 3 and MVC 4</li><li>Visual Studio 2013 supports only MVC 4 and MVC 5</li><li>Visual Studio 2017 and Visual Studio 2015 supports MVC 4 (you can open existing projects but not create new ones) and MVC 5</li></ul><br/><br/>Upgrading MVC versions:<ul><li>For information about how to automatically upgrade from MVC 2 to MCV 3, see [ASP.NET MVC 3 Application Upgrader](http://go.microsoft.com/fwlink/?LinkID=238178).</li><li>For information about how to manually upgrade from MVC 2 to MVC 3, see [Upgrading an ASP.NET MVC 2 Project to ASP.NET MVC 3 Tools Update](http://go.microsoft.com/fwlink/?linkid=238178).</li><li>For information about how to manually upgrade from MVC3 to MVC 4, see [Upgrading an ASP.NET MVC 3 Project to ASP.NET MVC 4](http://www.asp.net/whitepapers/mvc4-release-notes). If your project targets .NET Framework 3.5 SP1, you must retarget it to use .NET Framework 4.</li><li>For information about how to manually upgrade from MVC 4 to MVC 5, see [How to Upgrade an ASP.NET MVC 4 and Web API Project to ASP.NET MVC 5 and Web API 2](https://www.asp.net/mvc/overview/releases/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2)</li></ul> |
+| Model-View-Controller framework (ASP.NET MVC) | Support for MVC versions and Visual Studio:<ul><li>Visual Studio 2010 SP1 supports MVC 2 and MVC 3; MVC 4 support is added through the [ASP.NET 4 MVC 4 for Visual Studio 2010 SP1 download](https://www.microsoft.com/en-us/download/details.aspx?id=30683)</li><li>Visual Studio 2012 supports only MVC 3 and MVC 4</li><li>Visual Studio 2013 supports only MVC 4 and MVC 5</li><li>Visual Studio 2015 supports MVC 4 (you can open existing projects but not create new ones) and MVC 5</li><li>Visual Studio 2017 supports MVC 5 by default when the **ASP.NET and web development** workload is installed. To add MVC 4 support (opening existing projects but not creating new ones), select the **ASP.NET MVC 4** option for that workload on the right-hand side of the installer.</li></ul><br/><br/>Upgrading MVC versions:<ul><li>For information about how to automatically upgrade from MVC 2 to MCV 3, see [ASP.NET MVC 3 Application Upgrader](http://go.microsoft.com/fwlink/?LinkID=238178).</li><li>For information about how to manually upgrade from MVC 2 to MVC 3, see [Upgrading an ASP.NET MVC 2 Project to ASP.NET MVC 3 Tools Update](http://go.microsoft.com/fwlink/?linkid=238178).</li><li>For information about how to manually upgrade from MVC3 to MVC 4, see [Upgrading an ASP.NET MVC 3 Project to ASP.NET MVC 4](http://www.asp.net/whitepapers/mvc4-release-notes). If your project targets .NET Framework 3.5 SP1, you must retarget it to use .NET Framework 4.</li><li>For information about how to manually upgrade from MVC 4 to MVC 5, see [How to Upgrade an ASP.NET MVC 4 and Web API Project to ASP.NET MVC 5 and Web API 2](https://www.asp.net/mvc/overview/releases/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2)</li></ul> |
 | Modeling | If you allow Visual Studio to update the project automatically, you can open it in Visual Studio 2015, Visual Studio 2013, or Visual Studio 2012.<br/><br/>The format of the modeling project has not changed between Visual Studio 2015 and Visual Studio 2017 and the project can be opened and modified in either version. However, there are differences in behavior in Visual Studio 2017:<ul><li>Modeling projects are now referred to as “Dependency Validation” projects in the menus and templates.</li><li>UML diagrams are no longer supported in Visual Studio 2017. UML files are listed in the Solution Explorer as before but will be opened as XML files. Use Visual Studio 2015 to view, create, or edit UML diagrams.</li><li>In Visual Studio 2017, validation of architectural dependencies is no longer performed when the modeling project is built. Instead, validation is carried out as each code project is built. This change does not affect the modeling project, but it does require changes to the code projects being validated. Visual Studio 2017 can automatically make the necessary changes to the code projects ([more information](http://go.microsoft.com/fwlink/?LinkId=827800)).</li></ul> |
 | MSI Setup (.vdproj) | See InstallShield Projects above. | 
 | Office 2007 VSTO | Requires a one-way upgrade for Visual Studio 2017. |

docs/python/debugging-cross-platform-remote.md

@@ -106,7 +106,10 @@ In these steps we'll set a simple breakpoint to stop the remote process.
 
 1. In the **Attach to Process** dialog that appears, set **Connection Type** to **Python remote (ptvsd)**. (On older versions of Visual Studio these are named **Transport** and **Python remote debugging**.)
 
-1. In the **Connection Target** field (**Qualifier** on older versions), enter `tcp://<secret>@<ip_address>:5678` where `<secret>` is the string passed `enable_attach` in the Python code, `<ip_address>` is that of the remote machine (which can be either an explicit address or a name like myvm.cloudapp.net), and `:5678` is the remote debugging port number. 
+1. In the **Connection Target** field (**Qualifier** on older versions), enter `tcp://<secret>@<ip_address>:5678` where `<secret>` is the string passed `enable_attach` in the Python code, `<ip_address>` is that of the remote machine (which can be either an explicit address or a name like myvm.cloudapp.net), and `:5678` is the remote debugging port number.
+
+    > [!Warning]
+    > If you're making a connection over the public internet, you should be using `tcps` instead and following the instruction below for [Securing the debugger connection with SSL](#securing-the-debugger-connection-with-ssl).
 
 1. Press Enter to populate the list of available ptvsd processes on that machine: