You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd like to build a robust testing infrastructure for different Operating Systems (including windows) and provide the same level of support for Windows CLI users as other OSs. Where possible, we need to include Windows as a standard part of our testing infrastructure.
Given powershell is now available out of box in newer version of windows, we're going to align docs to powershell (not cmd).
The text was updated successfully, but these errors were encountered:
One exception though is cmd.exe (used among other things to execute batch files), which has its own argument splitting logic. That forces the standard library to implement custom escaping for arguments passed to batch files. Unfortunately it was reported that our escaping logic was not thorough enough, and it was possible to pass malicious arguments that would result in arbitrary shell execution.
I don't think this is an issue for our use of Command. However, we should look into our deps and update rust version.
All Rust versions before 1.77.2 on Windows are affected, if your code or one of your dependencies executes batch files with untrusted arguments. Other platforms or other uses on Windows are not affected.
We'd like to build a robust testing infrastructure for different Operating Systems (including windows) and provide the same level of support for Windows CLI users as other OSs. Where possible, we need to include Windows as a standard part of our testing infrastructure.
Given powershell is now available out of box in newer version of windows, we're going to align docs to powershell (not cmd).
The text was updated successfully, but these errors were encountered: