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
For teams that work on non-Windows OS as their development platform, they can make files that have names that are not compatible with the Windows OS. When submitting a SAST scan, the clone executes on Windows and fails due to invalid filenames,
Files with invalid characters like "<" or ">" are part of the problem. Windows also reserves names like "prn", "con", "lpt", and "aux" so that they are also invalid.
Proposed solution
Add a feature that can work in conjunction with CxFlow's local checkout where filename globs can be defined. CxFlow does the following:
Clones the repo that has code to be submitted for scanning.
Removes files that match any of the glob parameters (like <, aux, etc)
Submits the Windows-compatible files for scan.
Additional details
This affects users that are using CxFlow with webhooks.
The text was updated successfully, but these errors were encountered:
Describe the problem
For teams that work on non-Windows OS as their development platform, they can make files that have names that are not compatible with the Windows OS. When submitting a SAST scan, the clone executes on Windows and fails due to invalid filenames,
Files with invalid characters like "<" or ">" are part of the problem. Windows also reserves names like "prn", "con", "lpt", and "aux" so that they are also invalid.
Proposed solution
Add a feature that can work in conjunction with CxFlow's local checkout where filename globs can be defined. CxFlow does the following:
Additional details
This affects users that are using CxFlow with webhooks.
The text was updated successfully, but these errors were encountered: