[wp-trac] [WordPress Trac] #53236: Nonce lifespans are inaccurate and unintuitively affected by timezones
WordPress Trac
noreply at wordpress.org
Fri May 21 06:54:32 UTC 2021
#53236: Nonce lifespans are inaccurate and unintuitively affected by timezones
-------------------------------------------------+-------------------------
Reporter: lev0 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Date/Time | Version:
Severity: minor | Resolution:
Keywords: has-patch needs-testing needs-unit- | Focuses:
tests |
-------------------------------------------------+-------------------------
Comment (by Rarst):
I still disagree that this needs a code change.
1/2 code return seems to be a legacy thing that is not in active use by
core.
The very worst case scenario here is that nonce is only valid for 12 hours
(instead of maximum possible 24), which I think is still reasonable amount
that causes no issues in practice (or we would be permanently swamped in
complaints about it).
Could you please elaborate why is it important for your needs to rely on
1/2 return?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53236#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list