From dce54151ae52be0f286c3e2207329b2ee0da25e9 Mon Sep 17 00:00:00 2001 From: philsmd <921533+philsmd@users.noreply.github.com> Date: Thu, 16 Jan 2020 12:25:18 +0100 Subject: [PATCH] minor: fix type in README.md of test modules --- tools/test_modules/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/test_modules/README.md b/tools/test_modules/README.md index a8b4e5f2b..8f91e1828 100644 --- a/tools/test_modules/README.md +++ b/tools/test_modules/README.md @@ -3,7 +3,7 @@ Each module provides the functions `module_constraints`, `module_generate_hash` and `module_verify_hash`. * The `module_constraints` function should return the minimum and maximum length of the password, salt and the combination of password and salt in following order: password (pure), salt (pure), password (optimized), salt (optimized) and combination (optimized). -Each pair should be set to -1 if the hash mode is not supporting the appropriate field. For example, if a hash-mode does not support a salt, it should be set to -1. The last field (combination) is important if the the password and the salt is stored in the same buffer in the kernel (typically raw hashes only). +Each pair should be set to -1 if the hash mode is not supporting the appropriate field. For example, if a hash-mode does not support a salt, it should be set to -1. The last field (combination) is important if the password and the salt is stored in the same buffer in the kernel (typically raw hashes only). * The first parameter to `module_generate_hash` is the password, which can be either in ASCII or binary (packed) form. The second parameter is the salt *which can be undefined for unsalted hash modes). * The `module_verify_hash` function accepts a line from the cracks file, without the newline characters.