Tech Stuff
- Thread starter JDMeister
- Start date
- Thread starter
- #3
- Thread starter
- #4
Yesterday, I saw a post on NVIDIA’s announcement of open-source drivers for some of its most recent video cards. And Hackaday being huge proponents of open-source software and hardware, you’d think we’d be pouring the champagne. But it’s trickier than that.
Part of the reason that they are able to publish a completely new, open-source driver is that the secrets that they’d like to keep have moved into the firmware. So is the system as a whole more or less open? Yeah, maybe both.
With a more open interface between the hardware and the operating system, the jobs of people porting the drivers to different architectures are going to be easier. Bugs that are in what is now the driver layer should get found and fixed faster. All of the usual open-source arguments apply. But at the same time, the system as a whole isn’t all that much more transparent. The irony about the new NVIDIA drivers is that we’ve been pushing them to be more open for decades, and they’ve responded by pushing their secrets off into firmware.
Secrets that move from software to firmware are still secrets, and even those among us who are the most staunch proponents of open source have closed hardware and firmware paths in our computers. Take the Intel Management Engine, a small computer inside your computer that’s running all the time — even while the computer is “off”. You’d like to audit the code for that? Sorry. And it’s not like it hasn’t had its fair share of security relevant bugs.
And the rabbit hole goes deeper, of course. No modern X86 chips actually run the X86 machine language instructions — instead they have a microcode interpreter that reads the machine language and interprets it to what the chip really speaks. This is tremendously handy because it means that chip vendors can work around silicon bugs by simple pushing out a firmware update. But this also means that your CPU is running a secret firmware layer at core. This layer is of course not without bugs, some of which can have security relevant implications.
This goes double for your smartphone, which is chock-full of multiple processors that work more or less together to get the job done. So while Android users live in a more open environment than their iOS brethren, when you start to look down at the firmware layer, everything is the same. The top layer of the OS is open, but it’s swimming on top of an ocean of binary blobs.
How relevant any of this is to you might depend on what you intend to do with the device. If you’re into open source because you like to hack on software, having open drivers is a fantastic resource. If you’re looking toward openness for the security guarantees it offers, well, you’re out of luck because you still have to trust the firmware blindly. And if you’re into open source because the bugs tend to be found quicker, it’s a mix — while the top level drivers are made more inspectable, other parts of the code are pushed deeper into obscurity. Maybe it’s time to start paying attention to open source firmware?
Part of the reason that they are able to publish a completely new, open-source driver is that the secrets that they’d like to keep have moved into the firmware. So is the system as a whole more or less open? Yeah, maybe both.
With a more open interface between the hardware and the operating system, the jobs of people porting the drivers to different architectures are going to be easier. Bugs that are in what is now the driver layer should get found and fixed faster. All of the usual open-source arguments apply. But at the same time, the system as a whole isn’t all that much more transparent. The irony about the new NVIDIA drivers is that we’ve been pushing them to be more open for decades, and they’ve responded by pushing their secrets off into firmware.
Secrets that move from software to firmware are still secrets, and even those among us who are the most staunch proponents of open source have closed hardware and firmware paths in our computers. Take the Intel Management Engine, a small computer inside your computer that’s running all the time — even while the computer is “off”. You’d like to audit the code for that? Sorry. And it’s not like it hasn’t had its fair share of security relevant bugs.
And the rabbit hole goes deeper, of course. No modern X86 chips actually run the X86 machine language instructions — instead they have a microcode interpreter that reads the machine language and interprets it to what the chip really speaks. This is tremendously handy because it means that chip vendors can work around silicon bugs by simple pushing out a firmware update. But this also means that your CPU is running a secret firmware layer at core. This layer is of course not without bugs, some of which can have security relevant implications.
This goes double for your smartphone, which is chock-full of multiple processors that work more or less together to get the job done. So while Android users live in a more open environment than their iOS brethren, when you start to look down at the firmware layer, everything is the same. The top layer of the OS is open, but it’s swimming on top of an ocean of binary blobs.
How relevant any of this is to you might depend on what you intend to do with the device. If you’re into open source because you like to hack on software, having open drivers is a fantastic resource. If you’re looking toward openness for the security guarantees it offers, well, you’re out of luck because you still have to trust the firmware blindly. And if you’re into open source because the bugs tend to be found quicker, it’s a mix — while the top level drivers are made more inspectable, other parts of the code are pushed deeper into obscurity. Maybe it’s time to start paying attention to open source firmware?
- Thread starter
- #5
- Thread starter
- #6
- Thread starter
- #7
- Thread starter
- #8
- Thread starter
- #9
- Thread starter
- #10
- Thread starter
- #11
- Thread starter
- #12
- Thread starter
- #13
So a couple of days ago, a customer gave me two trash bags full of "Out Of Service" laptops
and a few other things.
Instead of calling and asking if I could upgrade/repair the computers, (She) stuck them in trash bags.
Looking over the "Stash", I find a functional Dell kitted out with an Intel i5, 8 gig ram, DVD and running Windows 7.
The hard drive was a bit tired, (This does happen) so I'm slipping in a 500 gig SSD as I type this.
It's all good..
and a few other things.
Instead of calling and asking if I could upgrade/repair the computers, (She) stuck them in trash bags.
Looking over the "Stash", I find a functional Dell kitted out with an Intel i5, 8 gig ram, DVD and running Windows 7.
The hard drive was a bit tired, (This does happen) so I'm slipping in a 500 gig SSD as I type this.
It's all good..
Last edited by a moderator:
- Thread starter
- #14
- Thread starter
- #15
- Thread starter
- #16
- Thread starter
- #17
- Thread starter
- #18
So I received a couple of HP "All In One" computers to "Refurb".
They were "Out Of Service" As I'm migrating all of the customers
new computers to Linux. (Dual boot for now, but the future is Linux)
One down, one to go. I removed the "Tired" SATA spinning hard drive
and installed a new Samsung SSD. Ten second boot times.
These will be donated to some kids, and the parents work for the HPs owner.
Nice for the kids to actually have a 23 inch screen and a fast SSD to do homework on.
They were "Out Of Service" As I'm migrating all of the customers
new computers to Linux. (Dual boot for now, but the future is Linux)
One down, one to go. I removed the "Tired" SATA spinning hard drive
and installed a new Samsung SSD. Ten second boot times.
These will be donated to some kids, and the parents work for the HPs owner.
Nice for the kids to actually have a 23 inch screen and a fast SSD to do homework on.
- Thread starter
- #19
- Thread starter
- #20