Signify fails to generate the factory key due to the secret key not having a .sec extension it seems. Script halts.
I tried to install signify from source in case this might have been an issue with the Debian's repository version, but that didn't help unfortunately.
bungee@BHQ-GOS:~/resign-android-image$ setx=1 ./resign-android-image /home/bungee/resign-android-image/202211-1 /home/bungee/resign-android-image/keys grapheneos raven 2022111000 --factory-zip --generate-keys --replace-boot /home/bungee/resign-android-image/magisk_patched-25200_mkEOB.img
Android 13 support is untested!
Already on '13'
Your branch is up to date with 'origin/13'.
Already on '13'
Your branch is up to date with 'origin/13'.
Already up to date.
Already up to date.
Already up to date.
MAKING /home/bungee/resign-android-image/keys/factory.sec with gen_signify_key
signify-openbsd: please use naming scheme of **keyname.pub** and keyname.sec
Failed to run: gen_signify_key /home/bungee/resign-android-image/keys/**factory.sec.cwhbl3.tmp** /home/bungee/resign-android-image/keys/factory.pub
Generating the keys manually and re-running the script allows me to proceed, but it is a hinderance.
chriswoope
commented
1 year ago
Signify fails to generate the factory key due to the secret key not having a .sec extension it seems. Script halts. I tried to install signify from source in case this might have been an issue with the Debian's repository version, but that didn't help unfortunately.
Generating the keys manually and re-running the script allows me to proceed, but it is a hinderance.