8 ms·
> "It turned out what to look through the files that were in private keys to sign with code", reports bartvbl, "In fact, in some batch files were the commands a
by mindslight 11y ago
> "It turned out what to look through the files that were in private keys to sign with code", reports bartvbl, "In fact, in some batch files were the commands and pass phrases that were needed."
A company finally holds up their end of the GPL by including all source needed to create a working build, and it's called a mistake!?
For every device requiring images to be signed with a specific key, this is exactly what the manufacturer should be forced to release!
- ryan-c 11y agoIf they're going to release the signing keys, why bother with signing?
- userbinator 11y agoIf you want to believe that the release was deliberate, then it's all part of the act - signing could've been just a point in a requirements document. https://news.ycombinator.com/item?id=10236827 https://news.ycombinator.com/item?id=10236827
- infamouscow 11y agoThis is the fundamental disagreement between Linus Torvalds and the FSF over the GPL.
- deleted 11y ago[deleted]
- eridius 11y agoThis is absolutely a mistake. The whole point of requiring the firmware to be signed with a specific private key is to prevent third parties from installing their own custom firmware (e.g. to prevent malicious actors from installing malware onto the device). If you want to let everyone install their own build, then just don't require the code signature (or, alternatively, create a program where third parties can request a certificate signed with your master, so they can then sign their own binaries, similar to how iOS development works). > For every device requiring images to be signed with a specific key, this is exactly what the manufacturer should be forced to release! What do you mean by "should" here? If the source is covered by GPLv3, then yeah, if they use code-signing they need to have some way to let you get around it. That's the point of the anti-tivoization clause. But if the software is distributed under GPLv2, or any other license, then there's no anti-tivoization restriction, and therefore no "should" about it.
- mindslight 11y ago> The whole point of requiring the firmware to be signed with a specific private key is to prevent third parties from installing their own custom firmware Yes, which is blatantly anti-GPL2. I really wish any Linux copyright holder would step up to the plate and force the argument that since code+signature is the functional unit, adding the signature makes a derivative work and its source must be released in the preferred form for modification. The entire point of the GPL2 is that a developer who creates code and receives a modified version back should be able to modify that instance of code - tivoization is entering into the license in bad faith. Of course going GPL3 would make for a more solid foundation for doing so, but clarifying this subject directly conflicts with the desires of the proprietary sponsors - Google etc.
- kinghajj 11y agoI was under the impression that while it may be against the spirit in which GPL2 was written, it was an oversight and the necessary changes were made to GPL3.
- mindslight 11y agoAs far as I know, it has never been litigated - there is enough work making manufacturers release anything called "source" as it is. People writing new software just go with the clarified GPL3. Based on Linus's views, the Linux kernel being GPL is a happy accident of history. We should be glad it wasn't BSD so we at least ended up with DD-WRT/AOSP/etc. But we also should keep pushing to preserve the freeedoms that fostered it.
- marcosdumay 11y agoThe problem is that most people releasing GPLv2 software were not involved at its creation, and are doing it for the bare text contents or completely unrelated reasons. The original goals of the creators are not a very relevant reason. Yes, the GPLv3 fixed that, and there was plenty of time for projects to migrate already. Linux won't migrate, Linus already explicitly stated so.
- 11y ago
- ambrop7 11y agoSurely one doesn't have to use the same certificates for the firmware verification of boot images and for the signing of Windows applications.
- ossreality 11y ago....... wtf are you talking about? why bother signing? why bother trying to have any security then? if you wanted to argue for allowing enrollment of one's own private keys, then I'd agree, but otherwise it seems like you're just parroting something without understanding what youre asking for.
- scrollaway 11y agoI think a lot of people here will agree with you in spirit, but this is getting very controversially received because it's unclear whether this was a "leak by incompetence" or an actual "we want to follow GPL2 and therefore we have to do this".
- dogma1138 11y agoIndeed what world would we be living in where people couldn't sign malware and even malicious drivers for rootkits using the keys of one of the largest home networking corporations.
- e3b0c 11y agoThen what's the purpose of signing in the first place? The keys for official releases are supposed to be kept by a trustworthy senior management or some people with highly restricted privilege. Also the software/firmware shipping process must be well audited if there are serious (not just pretending to be) security requirements. The keys should not be exposed to a random technician or a new hire who can possibly responsible for destroying your and your clients' businesses. It looks like they didn't have a quite "formal" shipping flow at least in this case.