Re:Reading privileged memory with a side-channel
by michaelermer on Wednesday January 03, 2018 @05:57PM
(#16066241)
Google's post is newer and has more insights, the registry article is now outdated.
Re:Reading privileged memory with a side-channel
by ece on Wednesday January 03, 2018 @06:29PM
(#16066500)
The register has more details. Worth a read.
Re:Reading privileged memory with a side-channel
by olliej on Wednesday January 03, 2018 @06:46PM
(#16066624)
the google site has the actual white papers detailing the attacks.
Re:Reading privileged memory with a side-channel
by ece on Wednesday January 03, 2018 @07:10PM
(#16066758)
The register has the tweet with actual code for spectre, and more details from the manufacturers and potential fixes. Seriosuly? They're both worth a read.
Re:Reading privileged memory with a side-channel
by lern_too_spel on Wednesday January 03, 2018 @07:18PM
(#16066803)
I think the point is that your quoted section of the reg article is not correct according to the new information from Google.
Re:Reading privileged memory with a side-channel
by ece on Wednesday January 03, 2018 @07:47PM
(#16066965)
@lern_too_spel
The AMD engineer could be right if talking about Ryzen, and/or he isn't mentioning user-user and user-kernel boundaries.
AMD isn't affected in nearly the same way as Intel/ARM are: https://twitter.com/ryanshrout/status/948683677244018689
"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 result in a page fault."