#36744: Improve/correct scrypt password hasher documentation
-------------------------------------+-------------------------------------
Reporter: Dmitry Chestnykh | Owner: Dmitry
Type: | Chestnykh
Cleanup/optimization | Status: closed
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"719db78a94f0c69301dbcafee0373b0c0a49dff0" 719db78]:
{{{#!CommitTicketReference repository=""
revision="719db78a94f0c69301dbcafee0373b0c0a49dff0"
[6.0.x] Fixed #36744 -- Improved scrypt password hasher docs.
- Corrected work_factor description and its requirements.
- Added block_size description.
- Changed parallelism description to mention computations, rather than
threads (currently it's not multithreaded.)
- For all of the above, added standard scrypt terminology (N, r, p).
- Mentioned that in multithreaded implementations, parallelism also
influences the memory requirements.
Backport of 0ca3a0661173b02e2cbb0183d8543e790e7e4a55 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36744#comment:6>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019ae875b109-d4de4dbb-f0ca-4816-ae60-60f3186e3ceb-000000%40eu-central-1.amazonses.com.
