Maybe it is possible to deploy the system with secure boot and a protected IDevId key by default, but allowing the user/owner to erase the key and disable secure boot? This way all use cases could be supported, including playing with the BL2 code etc.
(I'm sure all of you have noticed, but I'm just throwing out random thoughts without knowing anything about how hard they are to implement) Bjørn _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
