I don't think so.

No not all cpus are affected, not by a very long shot. Only ones that have speculative execution (through a vulnerable cache design). And from what they are saying/implying it has to be more than just a little branch prediction/prefetch, meaning it needs more fetching than that. I cant see this core falling into that category. But will see I guess.

If you dont have an mmu/cache then you are certainly not vulnerable to this category of problem.

Maybe this wordpress vulnerability?
http://thehackernews.com/2017/02/wordpress-exploit-patch.html

@T-NT

While let's encrypt is great when compared to not having anything.

There are conveniences ~$150 per year buys you with an okay wildcard certificate. Certificates being valid for a span of years... Free revocation and reissue all day every day (versus a few times in a week). ...wild card subdomain support, you don't need a new cert if you roll out a new host on newhost.domain.com . Tech support tickets.

The conveniences and stability a paid SSL solution provides are likely more attractive to onion.io than saving $150. What is time worth? You have more of it if you are not dicking around with a certificate with more points of failure-- I know that. And I say that as a fan and supporter of Let's Encrypt. They are doing great things over there and have no reservations against someone using a Let's Encrypt cert-- when it makes sense to.

The hardware is not capable of powering itself down.

At best the firmware could be made to halt, perhaps a slowed clock and an infinite loop or at the outside an actual execution halt.

Hi @Carl-Verbiest, the token referred to here is for the Onion Cloud, which is still in private beta. We will be releasing the Onion Cloud for public use in mid December. Please stay tuned! Once it has been released, there will be an app within the Console that will allow you to generate Oauth tokens and manage other activities in the cloud.