Robert Cannon

There is a better way of setting this value in this Stack Overflow answer. [Stack Overflow](https://stackoverflow.com/a/48030563/99679) But this is a big issue for PowerShell. It impacts xPackage, installing modules, calling...

I found that these registry settings fix the issue: ``` Registry SchUseStrongCrypto { Key = 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' ValueName = 'SchUseStrongCrypto' ValueType = 'Dword' ValueData = '1' Ensure = 'Present' } Registry...

Yes, because this has such a wide impact. You can Install-Module from a source that has disabled TLS1.1, for instance. Microsoft really needs to patch this to make it the...

Is there a work-around for this? We are seeing this behavior and it is blocking powershell usage on our hardened centos servers.

@alerickson I tried this command to install on a fresh image and it does not work: sudo -- sh -c 'umask 002; yum install -y powershell' I think I could...

Running this seems to fix problems with finding modules. But installing modules still does not work. ``` sudo chmod 755 -R /usr/local/share/powershell ``` Get-PackageProvider is still not working. Not sure...

I was able to fix the issues for us. As part of our image creation script, we were installing powershell, but also later running a script to install some modules...

/tmp/powershell_init.ps1 is our script for installing some common modules on the server. If you don't need that, you can omit that step. Glad I was able to help!

I find that when I try to run this in a dockerfile, that I can't get it to run because IdentityServer wants a license key. Adding this environment variable seems...

I am not sure if this is related, but it looks like if an EventSource (sqs in my case) is ready before the Sensor that is using it is ready,...