Open Ghufz opened 3 years ago
PSVersion 6.2.3
It is out support (or near the time). Please tests with latest PowerShell 7.1 release. Also the cmdlet is in PowerShellGet repository - please create new issue there.
PowerShellGet requires the signature to be issued by the same certificate authority in order to update. Since Cisco has a new root CA it fails and you need to use the -SkipPublisherCheck
switch to bypass it. I'd recommend moving this ticket over to https://github.com/PowerShell/PowerShellGet. As for getting past the error you need to run this command instead.
Install-Module -Name Cisco.IMC -Force -AcceptLicense -SkipPublisherCheck
GitHubPowerShellGet is the package manager for PowerShell - PowerShell/PowerShellGet
Thanks for your reply.
The expected workaround is Install-Module -Name Cisco.IMC -Force -AcceptLicense -SkipPublisherCheck
My question is during the life cycle of single module it can happen that the CA may changes, and this issue will persists.
This is still open. The update-module
CMDLET does not allow us to specify a -skippublishercheck
option. This Authenticode issue occurs on numerous modules (Vmware but also MS Graph!). Why can it not be addressed? It's very common for a developer of admin to want to update all modules ot the latest without messy workarounds to run install-module
. Have I missed something here?
@shockogit PowerShellGet is deprecated in favor of PSResourceGet. If you use that new module it doesn't have this issue as publisher checks aren't enabled by default.
Steps to reproduce
Expected behavior
Actual behavior
Update-module throws exception
Environment data