Skip to content
This repository was archived by the owner on Feb 24, 2021. It is now read-only.
This repository was archived by the owner on Feb 24, 2021. It is now read-only.

Vote: Signing Resource Modules #471

Description

Running DSC via the ARM Template extension offers great flexibility for automated setups. By default the execution policy on Windows 10 prevents the execution of not signed scripts. This will lead to workarounds lowering the default security settings. E.g. see this issue: dsccommunity/ComputerManagementDsc#199

Are there any plans to sign the DSC Resources?

CC: Daniel Scott-Raynsford (@PlagueHO)

Activity

  1. PlagueHO commented on Dec 15, 2018

    @PlagueHO
    Contributor

    Tagging Michael Greene (@mgreenegit) and Katie Kragenbrink (@kwirkykat) . Does the Azure DSC Extension configure Windows 10 VMs in Azure to allow unsigned DSC Resources (e.g. the DSC Resource Kit) to be used?

  2. PlagueHO commented on Jan 12, 2019

    @PlagueHO
    Contributor

    Hi Andi Krüger (@andikrueger) - sorry we haven't got a clear answer on this one. I'll try and make sure I bring this up at the next community call. It would be good if the Azure DSC extension helps us with this.

  3. stale commented on Feb 11, 2019

    @stale

    This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

  4. added
    staleThe issue or pull request was marked as stale because there hasn't been activity from the community.
    on Feb 11, 2019
  5. andikrueger commented on Mar 4, 2019

    @andikrueger
    Author

    I totally forgot about this issue and if I’m not mistaken we did miss it on the last community call as well.
    Hope we will talk about signing on the next call or any way on how to get around:-)

  6. removed
    staleThe issue or pull request was marked as stale because there hasn't been activity from the community.
    on Mar 4, 2019
  7. gaelcolas commented on Mar 15, 2019

    @gaelcolas
    Contributor

    Hi Andi Krüger (@andikrueger),
    I discussed it offline with Katie and there are no limitations we know of that would get in the way...
    The problem is that it needs some efforts to implement it within the release pipeline in place, and that does not seem like a top priority (relative to other tasks, and with limited resources).

    It is worth reminding you (all) that it would only apply to the Resource Modules owned, released, published by Microsoft, which is a limited number.

    I've added 👍 and 👎 at the top to allow people to show their interests.

  8. changed the title [-]Error: “Resource”.psm1 is not digitally signed[/-] [+]Vote: Signing Resource Modules[/+] on Mar 15, 2019
  9. added
    enhancementThe issue is an enhancement request.
    help wantedThe issue is up for grabs for anyone in the community.
    and removed
    needs investigationThe issue needs to be investigated by the maintainers or/and the community.
    on Mar 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementThe issue is an enhancement request.help wantedThe issue is up for grabs for anyone in the community.questionThe issue is a question.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions