Earlier quoted context omitted.
Why would users refuse to buy hardware that works 99.9999999999% of the time when they apparently have no problem buying software that works 99% of the time? Radioactive decays and cosmic particles flipping bits give an upper bound for reliability. You are not going to see low-background packages and rad-hard chips in your iPhone.
Radioactive decays and cosmic particles flipping bits give an upper bound for reliability well below 99.9999999999% If it works 99.9999999999%, then it has a failure rate of 0.0000000001%, or 1E-12. Considering that a modern CPU executes approximately 1E9 operations per second, and that regular HDDs have a worse-case BER of 1 in 1E14 bits, 1E-12 is actually rather horrible and the actual error rate of computer hardwa…
The mysterious case of the Linux Page Table Isolation patches
251–260 of 264 posts
Re: The mysterious case of the Linux Page Table Isolation patches
#252Looks like it is speculative execution based, and does not affect AMD https://lkml.org/lkml/2017/12/27/2 AMD processors are not subject to the types of attacks that the kernel page table isolation feature protects against. The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that access would resu…
maybe it has to do with CR3 register? https://patchwork.kernel.org/patch/10138835/ Edit: switched to link without AD cancer
Something like this: https://cyber.wtf/2017/07/28/negative-result-reading-kernel-...
Re: The mysterious case of the Linux Page Table Isolation patches
#253Earlier quoted context omitted.
Eh, that information is shared widely. Some decent googl-fu will get you the information you want. The difference is a lock-pick can't exploit 20,000 doors in 20 minutes.
There are definitely bypass tools for common lock mechanisms, whose mechanism of operation isn't readily google-able.
Re: The mysterious case of the Linux Page Table Isolation patches
#254This may or may not be related, but there is a Xen advisory embargoed until Thursday (see https://xenbits.xen.org/xsa/ ) and I am aware of at least one VM provider who scheduled emergency VM reboots across their entire fleet this week because the issue cannot be addressed through hot-patching.
I got around 10% of our Xen instances scheduled for reboot on Jan 4th, mostly long running instances. It's the first time I've seen that many instances scheduled at once.
Re: The mysterious case of the Linux Page Table Isolation patches
#255Re: The mysterious case of the Linux Page Table Isolation patches
#256Earlier quoted context omitted.
not sure on exact details, but I received one as well, on a free-tier account I had sitting around with an empty dynamodb table that was showing very high projected usage. it was enough that I logged in immediately thinking that account had been hacked. nope, still empty table, deleted it and went to bed. glad I wasn't the only one who got that.
Same here. Mine was on standby so I terminated it. I wasn't sure what was going on so I nuked everything cancelled my account and will hope for the best.
One tiny Ubuntu instance I barely used and then put on standby. Then terminated.
Ugh :(
Re: The mysterious case of the Linux Page Table Isolation patches
#257No ones hiding anything, this patchset was developed in the open for many many months. The hysteria and intrigue in this random tumblr blog is completely superfluous. It's a hardware bug anyway. Here is a good hint to when something is not being embargoed: there is a paper and a public demonstration.
Will you apologize for saying this if an embargo is lifted? It seems very likely to me that there is an embargo.