#25460: Inconsistent behaviour from TimestampSigner with two different
separators
------------------------------+--------------------------------------
Reporter: alexbarcelo | Owner: nobody
Type: Bug | Status: closed
Component: Core (Other) | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: signing | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
The signature "UeDD0RvkDeC7qHNrI9HettcfRCQ" is based on the value
"kapo99:1ZfASc". Now in the second case, the value as changed to
"kapo99/1ZfASc" so the same signature won't work.
--
Ticket URL: <https://code.djangoproject.com/ticket/25460#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.4d1b5e1309e869b687836fce5f5e4c79%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
