Skip to content

Commit ddc75b8

Browse files
Update README.md with kbds and what to do if you find a vulnerability (#1369)
* Update README.md * ctrl cmd * add other instructions for logs
1 parent 9b511a5 commit ddc75b8

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

README.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,11 @@ to file an issue on our GitHub repository:
9898
Make sure to fill in the information that is requested in the issue template as it
9999
will help us investigate the problem more quickly.
100100

101-
> 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.
101+
To automatically create a bug report from within the extension, open the Command pallet (<kbd>Ctrl</kbd>/<kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>) 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.
102+
103+
NOTE: If you believe that there is a security vulnerability in the PowerShell extension for VSCode,
104+
it **must** be reported to [[email protected]](https://technet.microsoft.com/security/ff852094.aspx) to allow for [Coordinated Vulnerability Disclosure](https://technet.microsoft.com/security/dn467923).
105+
**Only** file an issue, if [email protected] has confirmed filing an issue is appropriate.
102106

103107
### 2. Capture verbose logs and send them to us
104108

@@ -115,6 +119,8 @@ that, zip up the logs in the corresponding folder for your operating system:
115119
- **Windows**: `$HOME\.vscode\extensions\ms-vscode.PowerShell-<CURRENT VERSION>\logs`
116120
- **Linux and macOS**: `~/.vscode/extensions/ms-vscode.PowerShell-<CURRENT VERSION>/logs`
117121

122+
Alternatively, you can open the log folder using the Command pallet (<kbd>Ctrl</kbd>/<kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>) and running the *"Open powerShell Extension Logs Folder"* command.
123+
118124
You have two options for sending us the logs:
119125

120126
1. If you are editing scripts that contain sensitive information (intellectual property,

0 commit comments

Comments
 (0)