News for hackers. Stuff that matters.
Re:Freedom and security issues on x86 platforms by darpa_escapee on Monday April 04, 2016 @12:00PM (#11422903)
ARM architectures also suffer from this. You'll be hard pressed to find a board that doesn't require a propriety board support package somewhere in the stack.

Ironically, it is usually the bootloader that is/requires a blob or it is the DTB.

I remember being in middle school and reading Stallman's articles on the dangers of a TPM-oriented push by manufacturers. As cliche as it is, Stallman was right.

The push for platform security is also a push for platform ownership. Tinkering/hacking/your ability as a hardware owner is at ends with corporate security needs and that is a shame.

Re:Freedom and security issues on x86 platforms by makomk on Monday April 04, 2016 @01:13PM (#11423554)
Most Allwinner chips can run an entirely open-source stack and there's quite a few hobbyist-oriented boards out there based on them. (Technically the ROM bootloader is closed source, but all it does is load your choice of bootloader into RAM and execute it. After that you have full control, including the ability to run code in TrustZone mode and on the supervisor CPU core if one exists.)
Re:Freedom and security issues on x86 platforms by xorblurb on Monday April 04, 2016 @05:39PM (#11425912)
IIRC Allwinner does not have public datasheets, and honestly I prefer to have an half-documented half-accessible x86 platform rather than a theoretically fully-accessible ARM one that in practice is 1/10 publicly usable (the cpu alone is not enough to have fun with a platform... especially in the ARM SoC world -- and existing drivers have never replaced a good documentation of the hardware they drive.)
Re:Freedom and security issues on x86 platforms by ashitlerferad on Tuesday April 05, 2016 @02:28AM (#11428287)
Security issues in ROM are still security issues. Even if it is in ROM, it still needs to be auditable.
Re:Freedom and security issues on x86 platforms by ashitlerferad on Monday April 04, 2016 @12:04PM (#11422944)
There are plenty of boards that run using mainline u-boot and mainline Linux, you can often ignore the vendor BSP.

You are right about ARM though, TrustZone is another DRM-oriented aspect of ARM-based SoCs.

Re:Freedom and security issues on x86 platforms by tremon on Monday April 04, 2016 @12:42PM (#11423264)
While TrustZone can implement DRM, it is not a closed management engine. If you control the board, you can load your own OS there (but, conversely, if you cannot load your own OS there, you do not control the board).

There was a talk at FOSDEM this year about using TrustZone to run a small hypervisor: https://fosdem.org/2016/schedule/event/microkernels_genode_u...

Re:Freedom and security issues on x86 platforms by kabdib on Monday April 04, 2016 @01:09PM (#11423516)
The boot ROMs on these things are proprietary, though. The vendors I've talked with have been extremely coy about what's in them (got an overview from Marvell once, spent a day looking at code on a projector screen and getting a walkthrough. They could have hidden much).
Re:Freedom and security issues on x86 platforms by duskwuff on Monday April 04, 2016 @05:39PM (#11425909)
The boot ROM typically gets out of your way pretty quickly, though. At worst it means you have to deal with some firmware-signing nonsense before chaining into a Linux kernel (or U-Boot); it isn't active in a running system.
Re:Freedom and security issues on x86 platforms by kabdib on Monday April 04, 2016 @06:03PM (#11426102)
I should add that the code we saw may not have been the code that was actually run. It had reset vectors and whatnot, but that's no guarantee there were no hidden ROMs that ran code before the code we reviewed got run. And it's certainly no guarantee there are no hidden hardware-level state machines that unlock . . . things. Things like ignoring X bits in pages, or being able to do some low-bandwidth computation with code embedded at the stenographic level.
Re:Freedom and security issues on x86 platforms by ctz on Monday April 04, 2016 @12:33PM (#11423186)
TrustZone is just another processor mode and associated memory protection, nothing more, nothing less.

It's equally as incoherent to say supervisor mode and the MMU is 'DRM-oriented'.

Re:Freedom and security issues on x86 platforms by ashitlerferad on Tuesday April 05, 2016 @02:30AM (#11428290)
In practice, TrustZone is for DRM.
Re:Freedom and security issues on x86 platforms by em3rgent0rdr on Monday April 04, 2016 @01:14PM (#11423556)
I'm using ASUS C201 which uses ARM. It was a Chromebook, now running libreboot and parabola linux.
Re:Freedom and security issues on x86 platforms by 5ilv3r on Monday April 04, 2016 @01:27PM (#11423673)
Can you share documentation? I have an upstream kernel running on my peach pit, but have not replaced uboot yet.
Re:Freedom and security issues on x86 platforms by em3rgent0rdr on Monday April 04, 2016 @06:15PM (#11426188)
Re:Freedom and security issues on x86 platforms by andrey_utkin on Monday April 04, 2016 @03:10PM (#11424499)
How is it regarding GPU driver (or what Mali is)? Are you running binary mali driver or FOSS lima?
Re:Freedom and security issues on x86 platforms by em3rgent0rdr on Monday April 04, 2016 @06:21PM (#11426224)
I don't really do GPU-intensive stuff on it. It renders webpages & youtube fine, which is probably the most graphical intensive stuff. I'm currently using it mostly for porting MuseScore to arm, mainly using qtcreator for development.

The external hdmi doesn't really work properly...I remember not being able to run external monitor in full screen, or at the same time as the lcd screen.

I just installed and ran glxgears. It gets 250 FPS and a default window size. But I do get an command line error libGL error: unable to load driver: rockchip_dri.so, so I don't think I'm getting GPU.

Re:Freedom and security issues on x86 platforms by revanx_ on Tuesday April 05, 2016 @08:09AM (#11429695)
There is no FOSS lima driver for Mali-T760. There was a lima dev working on it but cause of some e drama that went down the drain.
Re:Freedom and security issues on x86 platforms by grumble1234 on Tuesday April 05, 2016 @01:43AM (#11428116)
so jealous... I've tried to replicate that setup on my C201 but kept hitting issues. I might give it another shot some day soon. Does Libreboot make it easier to boot from SD/USB?
Re:Freedom and security issues on x86 platforms by revanx_ on Tuesday April 05, 2016 @08:17AM (#11429737)
off topic: do you happen to have any issues with the usb ports on the right side of the case?
Re:Freedom and security issues on x86 platforms by 5ilv3r on Monday April 04, 2016 @01:11PM (#11423533)
My dtb is generated from a dts at kernel compile time... Chromebook land is fun.
Re:Freedom and security issues on x86 platforms by darpa_escapee on Monday April 04, 2016 @04:00PM (#11425016)
Lucky. I have to hunt around for DTBs based on modified Rockchip and Freescale SoCs to update my devices.

I am unwilling to distribute said binaries to make it easier for people with the same hardware as I to update their 3 year old software. That, too, is a shame.

Re:Freedom and security issues on x86 platforms by astrobe_ on Monday April 04, 2016 @05:00PM (#11425620)
So it's not an "ARM architectures" issue. It's a problem between you and your provider, who for some reason is not willing to provide the DTS.

That said, given that DTB/DTS is an open spec, tools to reverse a DTB into a DTS should probably exist (like this one: http://forum.xda-developers.com/android/software-hacking/how...)

Re:Freedom and security issues on x86 platforms by rcxdude on Monday April 04, 2016 @05:48PM (#11425989)
You don't even need a secondary tool. The standard devicetree compiler, dtc, can convert a dtb back into a dts no problem. The dtb format is a pretty basic serialisation of the dts file, so fairly little information is lost (mainly pre-processor stuff like includes and some macros for constants) and you can easily round-trip.
Re:Freedom and security issues on x86 platforms by voltagex_ on Tuesday April 05, 2016 @03:01AM (#11428416)
On some boards, the dtb controls things like voltage to the eMMC, so getting it wrong can be catastrophic.
Re:Freedom and security issues on x86 platforms by bogomipz on Monday April 04, 2016 @12:42PM (#11423260)
DTB?
Re:Freedom and security issues on x86 platforms by tremon on Monday April 04, 2016 @12:44PM (#11423275)
Device tree blob. But FAFAIK that is just a binary decription of the hardware layout, and does not include (driver) code.