From e6b168c5d24fe04e460e1b9442ef57fa4f02ad1b Mon Sep 17 00:00:00 2001 From: Tyler James Leonhardt Date: Fri, 15 Jun 2018 10:44:42 -0700 Subject: [PATCH 1/3] Update README.md --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 70cb6cad78..e153dc2ef0 100644 --- a/README.md +++ b/README.md @@ -98,7 +98,11 @@ to file an issue on our GitHub repository: Make sure to fill in the information that is requested in the issue template as it will help us investigate the problem more quickly. -> Note To automatically create a bug report from within the extension run the *"Report a problem on GitHub"* command. Some basic information about your instance and powershell versions will be collected and inserted into a new GitHub issue. +To automatically create a bug report from within the extension, open the Command pallet (Ctrl+Shift+P) and run the *"Report a problem on GitHub"* command. Some basic information about your instance and powershell versions will be collected and inserted into a new GitHub issue. + +NOTE: If you believe that there is a security vulnerability in the PowerShell extension for VSCode, +it **must** be reported to [secure@microsoft.com](https://technet.microsoft.com/security/ff852094.aspx) to allow for [Coordinated Vulnerability Disclosure](https://technet.microsoft.com/security/dn467923). +**Only** file an issue, if secure@microsoft.com has confirmed filing an issue is appropriate. ### 2. Capture verbose logs and send them to us From c063b795611b7b01a405bd4e20f165c2580ba4de Mon Sep 17 00:00:00 2001 From: Tyler James Leonhardt Date: Fri, 15 Jun 2018 10:46:26 -0700 Subject: [PATCH 2/3] ctrl cmd --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e153dc2ef0..3129adc91b 100644 --- a/README.md +++ b/README.md @@ -98,7 +98,7 @@ to file an issue on our GitHub repository: Make sure to fill in the information that is requested in the issue template as it will help us investigate the problem more quickly. -To automatically create a bug report from within the extension, open the Command pallet (Ctrl+Shift+P) and run the *"Report a problem on GitHub"* command. Some basic information about your instance and powershell versions will be collected and inserted into a new GitHub issue. +To automatically create a bug report from within the extension, open the Command pallet (Ctrl/Cmd+Shift+P) and run the *"Report a problem on GitHub"* command. Some basic information about your instance and powershell versions will be collected and inserted into a new GitHub issue. NOTE: If you believe that there is a security vulnerability in the PowerShell extension for VSCode, it **must** be reported to [secure@microsoft.com](https://technet.microsoft.com/security/ff852094.aspx) to allow for [Coordinated Vulnerability Disclosure](https://technet.microsoft.com/security/dn467923). From 883c8e353184a9cf30f83edded7bf5cba66ba141 Mon Sep 17 00:00:00 2001 From: Tyler James Leonhardt Date: Fri, 15 Jun 2018 10:50:55 -0700 Subject: [PATCH 3/3] add other instructions for logs --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 3129adc91b..e4e273c129 100644 --- a/README.md +++ b/README.md @@ -119,6 +119,8 @@ that, zip up the logs in the corresponding folder for your operating system: - **Windows**: `$HOME\.vscode\extensions\ms-vscode.PowerShell-\logs` - **Linux and macOS**: `~/.vscode/extensions/ms-vscode.PowerShell-/logs` +Alternatively, you can open the log folder using the Command pallet (Ctrl/Cmd+Shift+P) and running the *"Open powerShell Extension Logs Folder"* command. + You have two options for sending us the logs: 1. If you are editing scripts that contain sensitive information (intellectual property,