Re:Spectre/Meltdown Pits Transparency Against Liability
by rayiner on Thursday February 01, 2018 @04:38PM
(#16286168)
“Results” is a loaded term. In computation, “results” means the return value of a computation. Intel does keep you from observing the result of secure_stuff. What it doesn’t do is clean up all the side effects.
[ Parent
| on HN ]
Re:Spectre/Meltdown Pits Transparency Against Liability
by pdpi on Thursday February 01, 2018 @04:58PM
(#16286315)
Speculative execution modifies observable state. What you call it is imaterial.
Re:Spectre/Meltdown Pits Transparency Against Liability
by dfox on Thursday February 01, 2018 @05:17PM
(#16286449)
The point there is that what spectre/meltdown exploits are sideffects that are not part of the architectural state as it is specified by any manufacturer. The whole issue points to the fact that security-wise the typical approach used for descriptions of CPU's architectural behavior is insufficient as there can be implementation-specific observable sideeffects that have security ramifications.
Re:Spectre/Meltdown Pits Transparency Against Liability
by rayiner on Thursday February 01, 2018 @05:01PM
(#16286339)
Words have meaning. The “result” of a computation is different from side effects. The distinction is important. Speculative execution will always modify “observable state.” E.g. power usage.
Re:Spectre/Meltdown Pits Transparency Against Liability
by mannykannot on Thursday February 01, 2018 @06:10PM
(#16286841)
'Results' and 'side-effects' are useful modifiers of 'modifies observable state', and the long-overlooked fact that the latter falls into the category is an important insight. I think you would find it very difficult to explain the problem or discuss possible solutions without making additional distinctions, beyond 'modifies observable state', with regard to what speculative execution does.
Re:Spectre/Meltdown Pits Transparency Against Liability
by gjjfdg on Thursday February 01, 2018 @08:35PM
(#16287643)
ELI5 is an internet acronym for "Explain like I'm five (years old)". In this example, "secure_stuff" may well be a call to a function that does not return any value. Some functions are like that. But if it isn't, we no longer are sure that the code in the else branch of the loop won't be able to deduce what would be returned as the result, thanks to Intel, no thanks to Intel.
Shame on you.