Replies: 1 comment
-
Looks like |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TG Version: 2.4.3
For the login form, when
POST login_handler
is hit, if there is already a session active it will return the currently active session id. Is it possible that each time that endpoint is hit, to generate a new session id and also modify the algorithm used for hashing the session id to increase entropy?I see in the repoze.who project they default to md5, would like to possibly use sha-256 instead:
https://github.com/repoze/repoze.who/blob/2f11841e41ecb7a455d92b899d457c781bf32967/repoze/who/_auth_tkt.py#L46
https://github.com/repoze/repoze.who/blob/master/repoze/who/plugins/auth_tkt.py#L48
Is that as simple as setting
"authtkt.digest_algo": hashlib.sha256
in theupdate_blueprint
config?Thank you!
Beta Was this translation helpful? Give feedback.
All reactions