aboutsummaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorOleksandr Suvorov2023-08-03 19:05:39 +0300
committerTom Rini2023-08-07 13:41:44 -0400
commit0d2761abbde00e1ff756426fdb77b4b30192311d (patch)
tree447aa58df9b0e5924ac46d36e2f325dd4ea592c7 /common
parenta536b2fdb10c6eb678fda6f239eb16414caf0496 (diff)
spl: remove duplicate SPL_MD5 option
There is another SPL_MD5 option defined in lib/Kconfig. Renaming SPL_MD5_SUPPORT introduced duplicate option with different description. As for now FIT and hash algorithm options are not related to each others, removing a duplicate option seems OK. Fixes: 4b00fd1a84c ("Kconfig: Rename SPL_MD5_SUPPORT to SPL_MD5") Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
Diffstat (limited to 'common')
-rw-r--r--common/spl/Kconfig12
1 files changed, 0 insertions, 12 deletions
diff --git a/common/spl/Kconfig b/common/spl/Kconfig
index bee231b583a..c66d70e2a99 100644
--- a/common/spl/Kconfig
+++ b/common/spl/Kconfig
@@ -561,18 +561,6 @@ config SPL_CRC32
for detected accidental image corruption. For secure applications you
should consider SHA1 or SHA256.
-config SPL_MD5
- bool "Support MD5"
- depends on SPL_FIT
- help
- Enable this to support MD5 in FIT images within SPL. An MD5
- checksum is a 128-bit hash value used to check that the image
- contents have not been corrupted. Note that MD5 is not considered
- secure as it is possible (with a brute-force attack) to adjust the
- image while still retaining the same MD5 hash value. For secure
- applications where images may be changed maliciously, you should
- consider SHA256 or SHA384.
-
config SPL_FIT_IMAGE_TINY
bool "Remove functionality from SPL FIT loading to reduce size"
depends on SPL_FIT