I mean, this doesn't really change anything from a practical perspective. It just highlights that the verbage in the press release was alarmist.
It's still a security concern that most users will be unaware of.
This is a most excellent place for technology news and articles.
I mean, this doesn't really change anything from a practical perspective. It just highlights that the verbage in the press release was alarmist.
It's still a security concern that most users will be unaware of.
Potato, potato....
Whether we call them 'undocumented commands' or a 'backdoor', the affect is more or less the same; a series of high-level commands not listed within the specs, preventing systems engineers/designers from planning around vulnerabilities and their potential for malicious use.
The dude that wrote this blog is a goof....
defines backdoor as “relating to something that is done secretly
effectively constitute a “private API”, and a company’s choice to not publicly document their private API
Idiot thinks these are two different things....
Are they are trying to argue that malicious intent is needed to define it as a back door?
Moron..
You’re very smart. I didn’t realize that until you called someone a goof, idiot and moron, but now it’s very clear that you have far superior intelligence.
Finally, some technical details that were sorely lacking from yesterday's article.
Anyway, having direct unprivileged R/W access to platform memory is indeed a security hole, no matter the vendor.
Anyway, having direct unprivileged R/W access to platform memory is indeed a security hole, no matter the vendor.
It is not. ESP32 is an embedded chip with less than one megabyte of RAM. It cannot run apps or load websites with any malicious code, it only runs the firmware that you flash on it, nothing else, and of course your firmware has full access to every chip feature. If your firmware has a security hole, it's not the chip's fault.
Try reading the article next time.