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.

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

Do not forcibly regenerate the session when session data changes #44

Closed

Conversation

rvm-peercode
Copy link

This is the responsibility of upper layers.

Closes: #43

Targeted to 1.12.x because the master branch doesn't exist.

Q A
Documentation no
Bugfix yes
BC Break no
New Feature no
RFC no
QA no

This is the responsibility of upper layers.

Closes: mezzio#43

Signed-off-by: Roel van Meer <roel.van.meer@peercode.nl>
@Ocramius Ocramius added Awaiting Maintainer Response Enhancement New feature or request Question Further information is requested RFC labels Oct 5, 2023
@rvm-peercode
Copy link
Author

@weierophinney Any chance that this can get your blessing?

@weierophinney
Copy link
Contributor

Regenerating the session on data change was a specific design goal of this component; it exists to help reduce the possibility of session hijacking and session replay attacks.

Changing it at this time would be a BC break, and require justification for the behavior change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BC Break Enhancement New feature or request Question Further information is requested RFC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Session regeneration during persistent is fragile, causes session loss
3 participants