+Michael, U-Boot mailing list Hi,
On 30 November 2014 at 19:26, Duxiaoqiang <duxiaoqi...@huawei.com> wrote: > > Hi Simon > > > > When I test verified boot with new version of U-boot and new version of > mkimage, I encountered a alignment problem about RSA public key exponents. > > > > I tested verified boot successful few months ago with version of 2014.07-rc4, > but failed with the same configuration and operations this time. > > > > Problem logs as below: > > > > > > I debug this problem and noticed that the problem was caused by > pulic_exponent’s address: 0xff78a04c, this address was not aligned to 8 byte, > but this address was pointed by a uint64 * type of pointer. > > Panic happened in function rsa_verify_with_keynode, just as below: > > > > By compared the u-boot.dtb file that signed with RSA public key, I noticed > that there are differences about PUBLIC_EXPONENT. > > With the older version of mkimage, there’s no public exponent section. And > this problem only happens when I use the new version of mkimage tool. > > > > I also checked uboot’s code, it seems that there’s lack of mechanism to > guarantee the alignment about public exponent section. > > > > Can you give some suggestions about this problem. Appreciate your time. Copying Michael. Perhaps we need a safer version of fdt64_to_cpu()? But you might be the first to run this on aarch64. I have not tried it yet, but I do now have a platform. Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
