Fallout-build / Fallout-build/Fallout

Plugin signing & trust posture beyond v12 defaults

Open
#162 0 comments 0 reactions 0 assignees View on GitHub
enhancement target/backlog
Dominant language
C#
Stars
154
Forks
19
Avg merge
1d 22h
Merged PRs (30d)
15

Description

Capacity-permitting follow-on to the v12 plugin SDK.

## Idea

v12 ships full-trust, in-process plugin loading (RFC #100). This issue tracks the harder follow-on questions:

- Assembly signing requirements for plugins (Authenticode, NuGet package signing).
- AssemblyLoadContext-based isolation for untrusted plugins.
- A trust-posture knob on the host (`AllowUnsigned`, `RequireSignedBy`).
- Threat model: what attacks does signing actually mitigate in a build-time context?

## Why not now

Not committed for v12 — the default trust posture is fine for the actual v12 user (already runs arbitrary build code). Track for later if a use case shows up.

## Cross-ref

- RFC #4 / #100 (defines the v12 baseline).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.