On 11:00 Mon 16 Mar , Jan Lübbe wrote: > Hi, > > On Fr, 2015-03-13 at 16:49 +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > > you just need to have a unique ID on the HW and then use a x509 object > > to store it. then signed it with you CA. As only validated keys can be > > used, you can easly give a generated key for a specific HW. > > And this key will be valid only for this HW. > > Yes, this sounds useful. So you'd have a board-specific way to check the > unique ID constraint in an intermediate cert against the HW ID? yes more or less but but at the key itself as you will have to upload the key to the board. And the key will only be accepted to be stored as it will be valid and have the HW ID. And for the record remember if you want to use module in secured boot mode for the kernel you will have to use x509 certificate anyway. So why not to use the same principal. u-boot way is not what is doing today on the market for authentication format. Today it's x509 or PGP. So I do prefer to stay as standard as possible, this does not mean we can not support the FTD stuff. But IMHO it's not the right way. We may have to even support the Microsoft format. Specially if we want to be able one day (my personnal target) a real replacement for grub2 too. Best Regards, J. _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
