PowerShell sans AMSI #24750
Replies: 2 comments 8 replies
-
|
I need the same patches for WASM Browser, WASI and Android where there is no AMSI or Telemetry is not possible. |
Beta Was this translation helpful? Give feedback.
-
|
That sounds like an excellent idea. I did notice LEGACYTELEMETRY definitions used to remove sections of code. I would recommend positive definitions, eg ENABLE_FEATURE_AMSI etc rather than negative ones. |
Beta Was this translation helpful? Give feedback.
-
|
It was intentional. |
Beta Was this translation helpful? Give feedback.
-
|
On the other hand there is only one platform that supports AMSI and a dozen or more that don't. So really it should only be enabled on the one platform. |
Beta Was this translation helpful? Give feedback.
-
|
Well, this has breathed new life into PowerShell...
Loading ASP.NET run time is as simple as Program.ps1 This works with the standard dotnet runtime irrespective of where it is installed, version or operating system. Then I can simply use New-AspNetForPowerShellWebApplication. |
Beta Was this translation helpful? Give feedback.
-
|
You should have a look on ReadyToRun and SharedFramework, it's disabled in the repo. |
Beta Was this translation helpful? Give feedback.
-
Yes, I set the SelfContained=False in powershell-win-core.csproj and powershell-unix.csproj. |
Beta Was this translation helpful? Give feedback.
-
|
I guess this is the missing piece |
Beta Was this translation helpful? Give feedback.
-
Alas yes. I now have both SelfContained=false and PublishReadyToRun=false and Windows MSI are now down to ~20MB and Debian packages down to ~12MB. |
Beta Was this translation helpful? Give feedback.
-
|
@rhubarb-geek-nz if you want to test single file bundle, I test it on Windows, you will find the needed config here. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It has been firmly established that AMSI logging within PowerShell is non-negotiable.
However if you have use cases where you don't want to accept the overhead you may consider trying PowerShell sans AMSI.
This is a fork of PowerShell which removes AMSI logging, Telemetry and version update checking.
It also uses the dotnet shared runtime rather than packaging its own, this means you can use ASP.NET more easily directly from
pwsh.exe.Beta Was this translation helpful? Give feedback.
All reactions