Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing signature #45

Closed
brainz80 opened this issue Jul 8, 2021 · 3 comments
Closed

Missing signature #45

brainz80 opened this issue Jul 8, 2021 · 3 comments
Assignees

Comments

@brainz80
Copy link

brainz80 commented Jul 8, 2021

When updating I get:

The version '1.5.0' of the module 'Configuration' being installed is not catalog signed. Ensure that      
the version '1.5.0' of the module 'Configuration' has the catalog file 'Configuration.cat' and signed     
with the same publisher 'CN=Joel H. Bennett, O=Joel H. Bennett, L=West Henrietta, S=New York, C=US'       
as the previously-installed module 'Configuration' with version '1.3.1' under the directory               
'%userprofile%\Documents\PowerShell\Modules\Configuration\1.3.1'. If you still want to install or        
update, use -SkipPublisherCheck parameter.                                                                
@nstrelow
Copy link

same problem here

@brainz80
Copy link
Author

brainz80 commented Aug 3, 2021

Took the risk and updated. To update I had to install the module Configuration with:

Install-Module Configuration -SkipPublisherCheck -Force

then remove the previous versions:

$Latest = Get-InstalledModule Configuration
Get-InstalledModule Configuration -AllVersions | Where-Object { $_.Version -ne $Latest.Version } | Uninstall-Module

haven't noticed any problems so far. Though hopefully the next updates will fix this issue.

@Jaykul
Copy link
Member

Jaykul commented Aug 28, 2021

I am sorry about that. I've let my code-signing certificates lapse.
Frankly, during 2020 the process for renewing them was broken.

I'm not sure if I'll renew them or now. I'm really not convinced anyone cares about code signing of PowerShell modules except when it breaks something because PowerShell hates it when you change signing certs (or stop signing like this). Based on that it seems that not signing is the safer option.

The work-around is to Install-Module Configuration -SkipPublisherCheck -Force as suggested above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants