3 ms·

Do you really think there is no such things (unpublished) in the Nordic BLE stack?

• a1369209993 8y ago
  There are definitely (unpublished, and possibly unfound) vulnerabilities in the Nordic stack. The point (IIUC) is that the Nordic stack can be fixed once those vulnerabilities are known. The TI stack, on the other hand, is in ROM; if^Wwhen it's broken, it's broken forever. (And that appears to have happened just now.)
  • lathiat 8y ago
    Nordic <3 They are doing great stuff
  • skaevola 8y ago
    I can't speak to the CC26xx series specifically, but normally deeply embedded cores running a ROM stack like that have some additional SRAM which can be loaded at boot for firmware patches.
• dcbadacd 8y ago
  I'm interested in building a security-sensitive project with Nordic's stack, are there no ways to isolate their "softdevice" from the rest of the code running on the SoC?
  • SlowRobotAhead 8y ago
    The softdevice binary runs in supervisor mode and typically does all its work in one of two interupt contexts. So... it gets its own ram, rom, and you can’t (not supposed to anyhow) access it. So... no, to answer your question, but depends on what you are trying to prevent I guess. You don’t need to run the softdevice at all, can shut off it down temporarily like while doing some crypto work, but if there was an exploit it seems like it could be bad because the SD seems like it can probably do anything your code could plus some. Additionally with the ‘software interrupt’ peripheral it seems it has a built-in way to branch to any arbitrary code location. However... there is a gambling application that uses one and the code has been through a couple audits as I was told.