Windows Client Guidance against speculative execution vulnerabilities
-
Hmmm.. that one does need some updating...seems all it has is the Win update fix.... firmware is non-compliant..
@Superfly
He has an AMD cpu, I believe. Does all that still apply?
-
-
50+ should be called the "Lead" years, because every year older you get, it feels like the more lead in your a$$
I wish I was 50
-
-
Hi,
Ironic how AMD calls it "AMD Secure Processor"
If the PS scripts tells you that the CPU is not secure yet then you can trust that.
Cheers,
-
-
Ok, I see. AMD has a flaw similar to the Intel ME issue.
-
Ok, I see. AMD has a flaw similar to the Intel ME issue.
It seems so, they just published the article today.
-
Makes one wonder just what other flaws are likely to be discovered or if any processor has ever actually been secure or with the rate these "security" experts are discovering flaws, ever will be.
-
Nobody would have known about this(not even the black hats) and it have been fixed eventually and quietly with some updates in the effected OS's and still supported hardware BIOS, and no one would have been the wiser, not even the bad guys.
But for some dumba** Linux kernel developer that tagged his code with a #comment, and being open source it was quickly seen by someone else and that dumba** told the media
-
Makes one wonder just what other flaws are likely to be discovered or if any processor has ever actually been secure or with the rate these "security" experts are discovering flaws, ever will be.
I suggest no processor is provably secure or error free - discuss.
-
-
In Windows 17046 I start Powershell as Administrator. I check policyexecution status. Then I run Install-Module SpeculationControl. I get this:
Attachment 171030
What am I doing wrong?
EDIT: Works okay in 16299.192.
Solved in build 17046 with Powershell command Set-PSRepository psgallery -InstallationPolicy trusted which prompted me to install the latest version of NuGet. Credit to MaxMVP in a Reedit post found here.