pwd_mkdb: default to network (big) endian hash order
For cross-architecture reproducibility. The db(3) functions work with hashes of either endianness, and the current (v4) version password db entries already store integers in network order. Do so with the hash as well so that identical password databases can be created on big- and little-endian hosts. The -B and -L flags exist to set the endianness for legacy (v3) entries when the -l flag is used, and they will still control hash endianness (at least until the backwards compatibility infrastructure is removed). MFC after: 1 week Sponsored by: The FreeBSD Foundation
This commit is contained in:
parent
7cd794214a
commit
e936bb9f69
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=332902
@ -77,7 +77,7 @@ static HASHINFO openinfo = {
|
|||||||
256, /* nelem */
|
256, /* nelem */
|
||||||
2048 * 1024, /* cachesize */
|
2048 * 1024, /* cachesize */
|
||||||
NULL, /* hash() */
|
NULL, /* hash() */
|
||||||
BYTE_ORDER /* lorder */
|
BIG_ENDIAN /* lorder */
|
||||||
};
|
};
|
||||||
|
|
||||||
static enum state { FILE_INSECURE, FILE_SECURE, FILE_ORIG } clean;
|
static enum state { FILE_INSECURE, FILE_SECURE, FILE_ORIG } clean;
|
||||||
|
Loading…
Reference in New Issue
Block a user