PowerShell / PowerShell/DSC

Apple could not verify “dsc” is free of malware

Open
#701 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Enhancement Needs Triage
Dominant language
Rust
Stars
523
Forks
75
Avg merge
3d 16h
Merged PRs (30d)
24

Description

Summary of the new feature / enhancement

Apple doesn't like binaries not notarized so ./dsc will not launch on MacOS. This is after downloading the release files via github.

Proposed technical implementation details (optional)

From Claude:

This error message is appearing because macOS's security features (Gatekeeper) are preventing the DSC executable from running because it hasn't been notarized by Apple. This is a common security protection on newer macOS versions.

Here's how to resolve this issue:

Method 1: Using System Preferences (recommended)
  1. Instead of clicking "Move to Trash", click "Done"
  2. Open System Preferences (or System Settings on newer macOS)
  3. Go to "Security & Privacy" or "Privacy & Security"
  4. In the "General" tab, you should see a message about "dsc" being blocked
  5. Click "Allow Anyway" or "Open Anyway"
  6. Try running the DSC command again, and you'll get a prompt asking if you're sure - click "Open"
Method 2: Using Terminal to bypass Gatekeeper for this specific app
  1. Open Terminal
  2. Run the following command (assuming the DSC tool is in your downloads folder):
    xattr -d com.apple.quarantine /path/to/dsc
    
    Replace "/path/to/dsc" with the actual path to the DSC executable
Method 3: Temporarily reduce security settings (not recommended)

If you're still having issues, you can temporarily allow apps from anywhere:

  1. Open Terminal
  2. Run: sudo spctl --master-disable
  3. Use the app
  4. Re-enable security: sudo spctl --master-enable

The first method is usually the safest and most straightforward. After allowing the app once, you shouldn't see this warning again for this particular application.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the GitHub release files for dsc and how the macOS executable is packaged. Confirm the Gatekeeper behavior on a downloaded release; done means the released dsc can launch on macOS without the documented quarantine or security-setting workarounds.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
operating-systems, release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.