mirror of
https://github.com/facebook/sapling.git
synced 2024-10-07 15:27:13 +03:00
9849c580fb
Content-Security-Policy (CSP) is a web security feature that allows servers to declare what loaded content is allowed to do. For example, a policy can prevent loading of images, JavaScript, CSS, etc unless the source of that content is whitelisted (by hostname, URI scheme, hashes of content, etc). It's a nifty security feature that provides extra mitigation against some attacks, notably XSS. Mitigation against these attacks is important for Mercurial because hgweb renders repository data, which is commonly untrusted. While we make attempts to escape things, etc, there's the possibility that malicious data could be injected into the site content. If this happens today, the full power of the web browser is available to that malicious content. A restrictive CSP policy (defined by the server operator and sent in an HTTP header which is outside the control of malicious content), could restrict browser capabilities and mitigate security problems posed by malicious data. CSP works by emitting an HTTP header declaring the policy that browsers should apply. Ideally, this header would be emitted by a layer above Mercurial (likely the HTTP server doing the WSGI "proxying"). This works for some CSP policies, but not all. For example, policies to allow inline JavaScript may require setting a "nonce" attribute on <script>. This attribute value must be unique and non-guessable. And, the value must be present in the HTTP header and the HTML body. This means that coordinating the value between Mercurial and another HTTP server could be difficult: it is much easier to generate and emit the nonce in a central location. This commit introduces support for emitting a Content-Security-Policy header from hgweb. A config option defines the header value. If present, the header is emitted. A special "%nonce%" syntax in the value triggers generation of a nonce and inclusion in <script> elements in templates. The inclusion of a nonce does not occur unless "%nonce%" is present. This makes this commit completely backwards compatible and the feature opt-in. The nonce is a type 4 UUID, which is the flavor that is randomly generated. It has 122 random bits, which should be plenty to satisfy the guarantees of a nonce. |
||
|---|---|---|
| .. | ||
| branches.tmpl | ||
| changelog.tmpl | ||
| changelogentry.tmpl | ||
| changeset.tmpl | ||
| error.tmpl | ||
| fileannotate.tmpl | ||
| filediff.tmpl | ||
| filelog.tmpl | ||
| filelogentry.tmpl | ||
| filerevision.tmpl | ||
| footer.tmpl | ||
| graph.tmpl | ||
| header.tmpl | ||
| index.tmpl | ||
| manifest.tmpl | ||
| map | ||
| notfound.tmpl | ||
| search.tmpl | ||
| shortlog.tmpl | ||
| shortlogentry.tmpl | ||
| tags.tmpl | ||