Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Tue, 14 Nov 2017 19:04:32 +0100
From: Frank Dittrich <>
Subject: Why would crypt_all() need/want to generate additional candidate


I just read the formats.h comment for the crypt_all function:

/* Computes the ciphertexts for given salt and plaintexts.
  * The count passed to cmp_all() must be equal to crypt_all()'s return 
  * If an implementation does not use the salt parameter or if salt is NULL
  * (as it may be during self-test and benchmark), the return value must 
  * match *count the way it is after the crypt_all() call.
  * The count is passed by reference and must be updated by crypt_all() 
if it
  * computes other than the requested count (such as if it generates 
  * candidate passwords on its own).  The updated count is used for c/s rate
  * calculation.  The return value is thus in the 0 to updated *count 
range. */

Why would crypt_all() generate additional candidate passwords on its own?
Are there any sample formats which make use of this weird feature?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.