I mean, there’s “secure boot” as a general concept, and then there’s “UEFI Secure Boot.”

The latter definitely had those concerns, especially around 2012 when it first became a thing and a lot of folks were concerned that Microsoft would try to use it to lock down devices to only run Windows. See also:

• https://softwarefreedom.org/blog/2012/jan/12/microsoft-confirms-UEFI-fears-locks-down-ARM/

• https://arstechnica.com/information-technology/2015/03/windows-10-to-make-the-secure-boot-alt-os-lock-out-a-reality/

The level of concern seems like it’s died down a lot since then, not really so much because the Free Software community “won” but because Microsoft backed off a little bit and everybody kind of got used to it (and also because, at this point, we’ve got bigger fish to fry jailbreak, such as Android devices and such). But that frog is still in the pot, and the water hasn’t cooled off…

As for the former, which is what this discussion is about since we’re obviously not talking about Microsoft or Windows, my cynicism is mostly about how secure boot is a feature obviously aimed at industrial/commercial users. In other words, it represents yet more distraction away from and neglect of the core constituencies – schoolchildren and hobbyists – that the Raspberry Pi Foundation is supposed to be serving.