mirror of
https://github.com/cwinfo/powerdns-admin.git
synced 2024-09-18 22:39:36 +00:00
52b704baeb
Setting this attribute on a cookie marks it as non-cross-site, so it is only send in requests to our own server. It is reasonable that no one else should need our session or csrf data. Setting it explicitly also prevents any issues from the ongoing change in browser behaviour [0] when it is unset. Seasurf supports the SameSite attribute starting with v0.3. As nothing obviously broke, I used the opportunity and updated all the way to the most recent version. The SeaSurf default for SameSite is already `Lax`, so it only needs to be set for the session cookie. [0] https://developers.google.com/search/blog/2020/01/get-ready-for-new-samesitenone-secure
33 lines
553 B
Plaintext
33 lines
553 B
Plaintext
Flask==1.1.2
|
|
Flask-Assets==2.0
|
|
Flask-Login==0.5.0
|
|
Flask-SQLAlchemy==2.4.4
|
|
Flask-Migrate==2.5.3
|
|
SQLAlchemy==1.3.19
|
|
mysqlclient==2.0.1
|
|
configobj==5.0.6
|
|
bcrypt>=3.1.7
|
|
requests==2.24.0
|
|
python-ldap==3.4.0
|
|
pyotp==2.4.0
|
|
qrcode==6.1
|
|
dnspython>=1.16.0
|
|
gunicorn==20.0.4
|
|
python3-saml
|
|
pytz==2020.1
|
|
cssmin==0.2.0
|
|
jsmin==3.0.0
|
|
Authlib==0.15
|
|
Flask-SeaSurf==1.1.1
|
|
bravado-core==5.17.0
|
|
lima==0.5
|
|
pytest==6.1.1
|
|
pytimeparse==1.1.8
|
|
PyYAML==5.4
|
|
Flask-SSLify==0.1.5
|
|
Flask-Mail==0.9.1
|
|
flask-session==0.3.2
|
|
Jinja2==3.0.3
|
|
itsdangerous==2.0.1
|
|
werkzeug==2.0.3
|
|
cryptography==36.0.2 |