Please feel free to provide feedback or file bugs here.

-certificate parameter needed on the Install-Module cmdlet

I have built an internal Powershell Gallery where all uploaded (Powershell related) items are signed but I am in an 'Allsigned' environment mandated from 'on high' that cannot be changed which means that every time someone uses the 'Install-Module' cmdlet at the moment, unless they're installing something directly from my, self-managed, internal Gallery, whatever they've decided to install and download can't work unless they go find it and sign it as a seperate step. It would present less of a barrier to adoption to people if the downloading of a module from a repository allowed them to run the downloaded .ps1, .psm1, .psd1, .ps1xml etc files affected by our AllSigned policy and sign them as they go (assuming that they have been granted or otherwise obtained a codesigning certificate already).

1 vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Clayton McKenzie shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base