#36744: Improve/correct scrypt password hasher documentation
-------------------------------------+-------------------------------------
               Reporter:  Dmitry     |          Owner:  Dmitry Chestnykh
  Chestnykh                          |
                   Type:             |         Status:  assigned
  Cleanup/optimization               |
              Component:             |        Version:  dev
  Documentation                      |
               Severity:  Normal     |       Keywords:
           Triage Stage:             |      Has patch:  1
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 The current documentation for scrypt password hasher lacks some
 constraints and definitions:

   1.  work_factor: described incompletely, missing the requirement that
 this value must be a power of  2
   2.  block_size: has no description
   3.  parallelism: needs to be defined, perhaps, as "independent
 computations" rather than "threads", because the current OpenSSL
 implementation is not multithreaded.

 If OpenSSL becomes multithreaded, the "Estimating memory usage" note also
 needs to be adjusted to account for parallelism.

 I think it would also be helpful to mention that these parameters are N,
 r, p, as these are standard terminology for those familiar with scrypt.

 I'll send a pull request shortly.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36744>
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/0107019a997d9c15-9d8d100f-6562-4a59-9fe8-75c6d8800bb4-000000%40eu-central-1.amazonses.com.

Reply via email to