4 ms·
Some of the "facts" here are pretty weak. The "years of security expertise" is not really a feature I'd be proud of given the recent processor-level vulnerabili
by jchw 8y ago
Some of the "facts" here are pretty weak. The "years of security expertise" is not really a feature I'd be proud of given the recent processor-level vulnerabilities that in fact, paint a very different picture about how traditional processor vendors treat security.
Even if there is some validity here, this is in surprisingly poor taste. I've known people who have worked for ARM. I wonder what they think about this.
- cptskippy 8y agoHow would an open source processor be better from a security perspective? I might still be a little shell shocked from my attempts to setup a MythTV Box 10 years ago but this is what's running through my head: "Did you RTFM?" "Debain CPU doesn't have that issue." "Just disable the ALUs in firmware, they're not necessary in modern processors anyways." "That's been patched, just download processor v2.3.4.432 and send it to your FAB, they should spin you a new CPU in 8-12 months."
- justinjlynn 8y agoAll of that sounds better than: "Oh, our new processors don't have that issue. Trust us, pay me. Oh, you just bought one? Too bad."
- jchw 8y agoSome open source projects are different. A lot of them do not cater to end users directly. But if you want to talk about open source security, take a look at how OpenBSD handles issues; they definitely aren't messing around.
- cptskippy 8y agoThat's all true, I'm just wondering how things would be different if everyone were using an Open Source CPU vs what we have today. If everyone is running the same CPU design but sourced from different manufacturers who had them spun up at different fabs, how would that affect support? Today we have one or two device manufacturers we rely on for support and answers about if security fixes can be done in firmware vs requiring a hardware fix. We can pull the CPU ID of our system and then check with AMD or Intel for an authoritative answer. What does that look like when anyone can manufacture a chip? Will there still end up being one or two predominant CPU manufactures for desktop/mobile/server CPUs to simplify support? Are we going to have to rely on OEMs to support the CPUs they put in their machines? I'm fearful we might end up in a situation similar or worse to what we have with Android where smartphones are shipped in their final state and never receive anything beyond failure support from the OEM/ODM.
- snom380 8y agoThat's the case today: ARM CPUs are sourced from different manufacturers and packaged together with other cores into SoCs, which have wildly varying support from their vendors. Some of these processors also have custom extensions. If you're worried about chip security when anyone can manufacture a chip, then sorry, we're already there, and RISC-V doesn't change that.
- cptskippy 8y agoSo what does it solve that's a problem today? * Serious question. Apart from the freedom and control aspects of the Open Source model, what is solved with an open source CPU architecture or what are the benefits? I can see being able to spin your own chips would enable an OEM/ODM to keep producing the same old design indefinitely where as reliance on Intel/AMD/Samsung/Mediatek means you have to refresh your design. That could be both a benefit and a detriment depending on how you look at it.
- snom380 8y ago
- snom380 8y agoWhile the comparison to MythTV for a fun coment, this is exactly what ARM would like the high level decision makers to feel. Just as Microsoft tried with their "get the facts" campaign years ago. Notwithstanding your terrible MythTV experience, there's seveal companies offering commercial support for Linux today, and a lot of effort has been put into making it as secure as the Windows equivalent. I suspect the same could happen with RISC-V.
- cptskippy 8y agoAnother comment mentioned Western Digital switching to RISC-V which makes a lot of sense and that's about it. I'm struggling to see how RISC-V would improve the situation with edge devices or personal computing devices where the implementations will probably end up being propriety in nature and beholden to the vendor for any updates. Even when we do get something like a custom ROM for a router or smartphone it will still be reliant on custom kernel modules or other lock-ins hindering open source support. It just feels like more of the same with a chance for ODMs to save some on the BOM while not passing the savings on to us. I guess it's just hard to get excited about it without seeing some sort of benefit to the end user. That doesn't mean I feel like we should stick with ARM or x86, I frankly don't care.
- deleted 8y ago[deleted]
- deepnotderp 8y agoOoO risc-v processors are also vulnerable to spectre...
- snvzz 8y agoWhich RISC-V processors?
- deepnotderp 8y agoAny of them unless they have specific modifications for mitigation.
- deepnotderp 8y agoAny of them that uses speculative execution to be clear, if it wasn't apparent.
- snvzz 8y agoPotentially.
- wlesieutre 8y agoRISC-V foundation says not: >No announced RISC-V silicon is susceptible, and the popular open-source RISC-V Rocket processor is unaffected as it does not perform memory accesses speculatively. https://www.techpowerup.com/240310/risc-v-foundation-issues-statement-on-spectre-meltdown-exploits https://www.techpowerup.com/240310/risc-v-foundation-issues-... Do you have a source?
- deepnotderp 8y agoThe rocket core isn't OoO, they even say so...
- wlesieutre 8y agoIt says right there "No announced RISC-V silicon is susceptible." Does someone actually make a RISC-V processor with out of order execution? Or is this a "They're going to make one eventually, so they'll have to address Spectre attacks before that happens" problem?
- vardump 8y agoWhile I wouldn't choose a new architecture so eagerly, existence of this page (if real) does to some extent validate RISC-V as a potential solution. Instead, of say, ARM M4+, A7, A53/A55, etc.
- blablabla123 8y agoYeah, this years of security scrutiny argument is getting disproved. The recent processor vulnerabilities are one example. Another is how big corporates treat internal software: upgrade rarely and test very extensively. This has proven very fatal: WannaCry wouldn't have been possible if people had been at least updating to the most recent release and update. I'd be happy to try out a RISC computer, actually it's quite sad that the CPU diversity got so little due to Intel/AMD.