mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-09-21 15:12:04 +00:00
e60e449931
SHA512_ALGO was used as a "either SHA512 or SHA384", although the implementations of these two algorithms share a majority of code. From a Kconfig interface perspective, it makes sense to present two distinct options. This requires #ifdefing out the SHA512 implementation from sha512.c. The latter doesn't make any sense. It's reasonable to say in Kconfig that SHA384 depends on SHA512, and seems to be the more polite way to handle the selection. Thus, automatically select SHA512 when SHA384 is enabled. Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
28 lines
704 B
Text
28 lines
704 B
Text
menuconfig CRYPT_PW
|
|
bool "Add crypt support for password-based unlock"
|
|
depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
|
|
help
|
|
Enable support for crypt-style hashed passphrases.
|
|
This will then be used as the mechanism of choice to
|
|
verify whether the entered password to unlock the
|
|
console is correct or not.
|
|
|
|
if CRYPT_PW
|
|
|
|
config CRYPT_PW_SHA256
|
|
bool "Provide sha256crypt"
|
|
select SHA256
|
|
select SHA256_ALGO
|
|
help
|
|
Enables support for the sha256crypt password-hashing algorithm.
|
|
The prefix is "$5$".
|
|
|
|
config CRYPT_PW_SHA512
|
|
bool "Provide sha512crypt"
|
|
select SHA512
|
|
select SHA512
|
|
help
|
|
Enables support for the sha512crypt password-hashing algorithm.
|
|
The prefix is "$6$".
|
|
|
|
endif
|