Re: u-boot in core182

["Peter Müller" <peter.mueller@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Hello Arne,

thank you for your e-mail, and for flagging this.

After enabling indirect branch tracking for user space in Core Update
179, I was under the impression that it would make sense to ship binaries
not included in that Core Update, when there is an occasion, even if
their version number has not changed.

If I'm not mistaken, we didn't touch u-boot since C179, so I thought
shipping the mkimage binary won't hurt, although the security benefit
of IBT is probably minimal in this case.

Should I revert the commit shipping mkimage in C182? What do you think?

Thanks, and best regards,
Peter Müller

> Hi Peter,
> 
> there is no need to ship u-boot in core182.
> This patch https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=ba1457912e82c80dd4ff59d2c45d8b523df81189https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=ba1457912e82c80dd4ff59d2c45d8b523df81189
> only remove an extra pass that was needed to build the kernel early in the build process which was moved to the end.
> The final u-boot binaries are the same.
> 
> Arne