Additionally, set the db hash to be in network byte order (big-endian) as with other integers in the database. The db(3) functions work with a hash of either endianness. Using a fixed endianness allows us to create a password database that's reproducible regardless of host endianness.
The -B and -L options were originally added to set the endianness of v3 records emitted by pwd_mkdb, but they also set the db hash endiannes and so have been retained temporarily.
Mentioned on the FreeBSD-Current and FreeBSD-Stable lists