Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add paragraph about origin-specific security headers being hard to use in EPUB #2013

Merged
merged 2 commits into from
Mar 2, 2022
Merged

Add paragraph about origin-specific security headers being hard to use in EPUB #2013

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6981fc0
Add paragraph about origin-specific headers being hard to use in EPUB
dlazin Feb 25, 2022
37d730d
Adjust language based on Ivan and Matt's comments
dlazin Mar 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions epub33/core/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8818,6 +8818,13 @@ <h3>Threat Model</h3>
<p>Checking for malware and exploits at distribution time is not always reliable, either, as the
malicious content can be swapped in any time after publication, unlike resources that come
embedded in the EPUB Container.</p>
<p>The <a href="#sec-container-iri">origin</a> of an EPUB is both unknown to the EPUB Creator and
specific to each Reading System implementation. Consequently, if the EPUB Creator hosts remote
resources on a web server they control, the server effectively cannot use security features that
require specifying allowable origins, such as headers for
<a href="https://fetch.spec.whatwg.org/#cors-protocol">CORS</a>,
<a href="https://www.w3.org/TR/CSP2/#content-security-policy-header-field"><code>Content-Security-Policy</code></a>,
or <a href="https://www.rfc-editor.org/rfc/rfc7034"><code>X-Frame-Options</code></a>.</p>
</dd>

<dt>Linking to external resources</dt>
Expand Down
7 changes: 7 additions & 0 deletions epub33/rs/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2156,6 +2156,13 @@ <h3>Threat Model</h3>
<p>Calls to remote resources can also be used to track information about users (e.g., through
server logs). Reading Systems should limit the information they expose through HTTP requests
to only what is essential to obtain the resource.</p>
<p>The <a href="#sec-container-iri">origin</a> of an EPUB is both unknown to the EPUB Creator and
specific to each Reading System implementation. Consequently, if the EPUB Creator hosts remote
resources on a web server they control, the server effectively cannot use security features that
require specifying allowable origins, such as headers for
<a href="https://fetch.spec.whatwg.org/#cors-protocol">CORS</a>,
<a href="https://www.w3.org/TR/CSP2/#content-security-policy-header-field"><code>Content-Security-Policy</code></a>,
or <a href="https://www.rfc-editor.org/rfc/rfc7034"><code>X-Frame-Options</code></a>.</p>
</dd>

<dt>External links</dt>
Expand Down