| 1 |
Source: flask-talisman |
| 2 |
Maintainer: Debian Python Team <[email protected]> |
| 3 |
Uploaders: Edward Betts <[email protected]> |
| 4 |
Section: python |
| 5 |
Priority: optional |
| 6 |
Build-Depends: debhelper-compat (= 13), |
| 7 |
dh-sequence-python3, |
| 8 |
python3-all, |
| 9 |
python3-flask, |
| 10 |
python3-pytest, |
| 11 |
python3-setuptools |
| 12 |
Rules-Requires-Root: no |
| 13 |
Standards-Version: 4.6.2 |
| 14 |
Homepage: https://github.com/wntrblm/flask-talisman |
| 15 |
Vcs-Browser: https://salsa.debian.org/python-team/packages/flask-talisman |
| 16 |
Vcs-Git: https://salsa.debian.org/python-team/packages/flask-talisman.git |
| 17 |
|
| 18 |
Package: python3-flask-talisman |
| 19 |
Architecture: all |
| 20 |
Depends: ${misc:Depends}, ${python3:Depends} |
| 21 |
Description: HTTP security headers for Flask |
| 22 |
Talisman is a small Flask extension that handles setting HTTP headers that can |
| 23 |
help protect against a few common web application security issues. |
| 24 |
. |
| 25 |
The default configuration: |
| 26 |
. |
| 27 |
* Forces all connects to https, unless running with debug enabled. |
| 28 |
* Enables HTTP Strict Transport Security. |
| 29 |
* Sets Flask's session cookie to secure, so it will never be set if your |
| 30 |
application is somehow accessed via a non-secure connection. |
| 31 |
* Sets Flask's session cookie to httponly, preventing JavaScript from being |
| 32 |
able to access its content. CSRF via Ajax uses a separate cookie and should |
| 33 |
be unaffected. |
| 34 |
* Sets X-Frame-Options to SAMEORIGIN to avoid clickjacking. |
| 35 |
* Sets X-XSS-Protection to enable a cross site scripting filter for IE and |
| 36 |
Safari (note Chrome has removed this and Firefox never supported it). |
| 37 |
* Sets X-Content-Type-Options to prevent content type sniffing. |
| 38 |
* Sets a strict Content Security Policy of default-src: 'self'. This is |
| 39 |
intended to almost completely prevent Cross Site Scripting (XSS) attacks. |
| 40 |
This is probably the only setting that you should reasonably change. See |
| 41 |
the Content Security Policy section. |
| 42 |
* Sets a strict Referrer-Policy of strict-origin-when-cross-origin that |
| 43 |
governs which referrer information should be included with requests made. |