dashboard/configs/linux: enable CONFIG_MODULE_SIG_SHA512 for all configs that have CONFIG_MODULE_SIG

[ajdlinux]

Some modern versions of OpenSSL don't like it when you use SHA1 signatures:

  80A20474797F0000:error:03000098:digital envelope routines:do_sigver_init:invalid digest:crypto/evp/m_sigver.c:342:
  make[4]: *** [.../certs/Makefile:53: certs/signing_key.pem] Error 1
  make[4]: *** Deleting file 'certs/signing_key.pem'
  make[4]: *** Waiting for unfinished jobs....
  make[3]: *** [.../scripts/Makefile.build:478: certs] Error 2
  make[2]: *** [.../Makefile:1936: .] Error 2
  make[1]: *** [.../Makefile:224: __sub-make] Error 2
  make[1]: Leaving directory '...'
  make: *** [Makefile:224: __sub-make] Error 2

For this reason, kernel commit f3b93547b91ad849b58eb5ab2dd070950ad7beb3 switches to MODULE_SIG_SHA512 by default, and yet:

android-5.15.config:CONFIG_MODULE_SIG_SHA1=y
android-5.15-cuttlefish.config:CONFIG_MODULE_SIG_SHA1=y
distros/android-google-gs-shusky-5.15-android14-qpr3:CONFIG_MODULE_SIG_SHA1=y
upstream-leak.config:CONFIG_MODULE_SIG_SHA1=y
android-5.15-cuttlefish-base.config:CONFIG_MODULE_SIG_SHA1=y
android-5.15-base.config:CONFIG_MODULE_SIG_SHA1=y
android-5.10.config:CONFIG_MODULE_SIG_SHA1=y
android-5.10-cuttlefish.config:CONFIG_MODULE_SIG_SHA1=y
android-5.10-cuttlefish-base.config:CONFIG_MODULE_SIG_SHA1=y
android-5.10-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-snapshot-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-snapshot-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
stable-6.1-arm64-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-smack-kasan.config:CONFIG_MODULE_SIG_SHA1=y
stable-6.1-arm64-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-smack-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
android14-5.15-cuttlefish.config:CONFIG_MODULE_SIG_SHA1=y
android-6.1.config:CONFIG_MODULE_SIG_SHA1=y
android-6.1-base.config:CONFIG_MODULE_SIG_SHA1=y
android14-5.15-cuttlefish-base.config:CONFIG_MODULE_SIG_SHA1=y
android-6.12-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-selinux-kasan.config:CONFIG_MODULE_SIG_SHA1=y
stable-5.4-kasan.config:CONFIG_MODULE_SIG_SHA1=y
android-6.12.config:CONFIG_MODULE_SIG_SHA1=y
stable-5.15-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
stable-5.4-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-selinux-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-apparmor-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-kasan-badwrites-base.config:CONFIG_MODULE_SIG_SHA1=y
stable-5.15-arm64-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
stable-5.15-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-kmsan-next-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-kasan_sw-kcov-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm-full-base.config:CONFIG_MODULE_SIG_SHA1=y
stable-5.15-arm64-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-riscv64-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-kasan_sw-kcov.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-mte.config:CONFIG_MODULE_SIG_SHA1=y
upstream-kmsan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-kmsan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-riscv64-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-mte-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-full.config:CONFIG_MODULE_SIG_SHA1=y
upstream-apparmor-kasan.config:CONFIG_MODULE_SIG_SHA1=y
upstream-rust-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-leak-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
stable-6.1-kasan-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm-full.config:CONFIG_MODULE_SIG_SHA1=y
upstream-kasan-badwrites.config:CONFIG_MODULE_SIG_SHA1=y
upstream-arm64-full-base.config:CONFIG_MODULE_SIG_SHA1=y
upstream-kmsan-next.config:CONFIG_MODULE_SIG_SHA1=y
upstream-rust-kasan.config:CONFIG_MODULE_SIG_SHA1=y
stable-6.1-kasan.config:CONFIG_MODULE_SIG_SHA1=y

I'm not exactly sure why this is, given we don't explicitly select it in any of the config bits AFAICT.

[a-nogikh]

Hmmm, that's a good question actually. I've double-checked the current KConfigs and the bits we set in https://github.com/google/syzkaller/tree/master/dashboard/config/linux/bits, I don't see why it would use a non-default option here.

My bet is that it has to do with how syzkaller parses/interprets Kconfig rules in https://github.com/google/syzkaller/tree/master/pkg/kconfig