Dear Maintainer,
I have a workaround solution meanwhile.
Create your own keys which will later be used with `mokutil` with the following script I have created for this scenario: https://codeberg.org/horsey_guy/MOK_Key_Create/raw/branch/main/create_keys.sh
You can now use `sbsign --key {SOME_NAME}.key --cert {SOME_NAME}.crt /boot/memtest86+x64.efi --output /boot/memtest86+x64.efi.signed` (cannot in-place sign)
Then symlink /boot/memtest86+x64.efi to /boot/memtest86+x64.efi.signed with `ln -sf /boot/memtestx86+64.efi.signed /boot/memtestx86+64.efi`.
The ia32 variants can be signed too.
Be sure to do the signing whenever memtest86+ is updated. You can make some sort of post-installation hook if that's possible to automate this.
Now use mokutil or else the keys will be rejected: `mokutil --import path/to/cert.der`
I have not tested this method although I will, but it should work as I have done some variation of this.
It would be nice if memtest86+ could be signed with Debian's keys though.
Sincerely,
Huey Chen