w3c / w3c/webappsec-csp

Allow nonce-source to be used in more directives.

Open
#116 16 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
224
Forks
93
Avg merge
18d 20h
Merged PRs (30d)
1

Description

I recently deployed nonce support on my site and it makes deploying a strong CSP considerably easier. A lot easier than I thought it was going to be now I've actually done it. One of the other aspects I liked was that my ridiculously huge script-src and style-src directives were cut down by more than 90%.

This got me thinking it'd be nice to simplify the rest of my policy and use nonces in other elements on the page. Things like img-src, child-src, frame-src and even the default-src perhaps?

Could we extend the nonce-source to be used more widely?

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 issue's proposed directives—img-src, child-src, frame-src, and default-src—and the existing nonce-source behavior in the CSP project. Define which directives should accept nonces and what compatibility or policy semantics would constitute completion; the payload names no files or tests to run.

Written by the indexing model from the issue text.

Assessment

Domain
security, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.