diff options
author | Jan Varho <jan@varho.org> | 2014-05-03 12:41:20 +0300 |
---|---|---|
committer | Technion <technion@lolware.net> | 2014-05-09 04:56:26 +0000 |
commit | 287236d6bf79702b3d4dca2907b34e2056a84afb (patch) | |
tree | b4e64a3a36221a04d738a5f45d5d2a3474a91ccb | |
parent | f850d6b3af1914361ae6ecbe5decb9474ae1443e (diff) |
Document that libscrypt_check modifies mcf
-rw-r--r-- | README.md | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -22,7 +22,7 @@ Libscrypt's easier to use interface wraps this up to deal with the salt and prod int libscrypt_hash(char *dst, char *passphrase, uint32_t N, uint8_t r, uint8_t p); -Sane constants have been created for N, r and p so you can create a has like this: +Sane constants have been created for N, r and p so you can create a hash like this: libscrypt_hash(outbuf, "My cats's breath smells like cat food", SCRYPT_N, SCRYPT_r, SCRYPT_p); @@ -35,6 +35,9 @@ Output stored in "outbuf" is stored in a standardised MCF form, which means incl mcf should be defined as at least SCRYPT_MCF_LEN in size. +Note that libscrypt_check needs to modify the mcf string and will not return it +to the original state. Pass it a copy if you need to keep the original mcf. + A number of internal functions are exposed, and users wishing to create more complex use cases should consult the header file, which is aimed at documenting the API fully. The test reference is also aimed at providing a well documented use case. |