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
This was an issue found while releasing 2.11.0 to Chocolatey (Choco). Since they run scans on packages via VirusTotal (VT), it would appear that some vendors are erroneously flagging the Private/Streams.ps1 file. The flagging is due to the file containing many functions which are for reading, altering, and writing to streams - which is seen as "potentially malicious" even though it's been used in perfectly valid context.
To save having to communicate with 10 different vendors, and allow Choco to publish the package without exemptions, a quick fix here could be as simple as moving the functions into the compiled .NET DLL - which could even help give a quick perf boost.
When the rewrite is done, a quick adhoc packaging locally and running the package via VT should show 0 violations.
The text was updated successfully, but these errors were encountered:
Describe the Change
This was an issue found while releasing 2.11.0 to Chocolatey (Choco). Since they run scans on packages via VirusTotal (VT), it would appear that some vendors are erroneously flagging the
Private/Streams.ps1
file. The flagging is due to the file containing many functions which are for reading, altering, and writing to streams - which is seen as "potentially malicious" even though it's been used in perfectly valid context.You can see an example here: https://www.virustotal.com/gui/file/1e89d36213e613f709588bf253193574bc47fbf4a797223a44ab7742a924676f
To save having to communicate with 10 different vendors, and allow Choco to publish the package without exemptions, a quick fix here could be as simple as moving the functions into the compiled .NET DLL - which could even help give a quick perf boost.
When the rewrite is done, a quick adhoc packaging locally and running the package via VT should show 0 violations.
The text was updated successfully, but these errors were encountered: