Re:Meltdown Update Kernel doesnt boot
by monk_e_boy on Wednesday January 10, 2018 @09:09PM
(#16120950)
I leave my machine on for weeks at a time. If something was scanning the memory even if it failed to find the location of my password 99.9% before it is erased eventually it will be lucky and get it.
Re:Meltdown Update Kernel doesnt boot
by brokenmachine on Wednesday January 10, 2018 @09:30PM
(#16121028)
Good point. I was only thinking about a single run but that makes sense.
Re:Meltdown Update Kernel doesnt boot
by Zakharov on Wednesday January 10, 2018 @11:29PM
(#16121394)
According to the paper, Meltdown can recover memory at about 500 kb/s
Re:Meltdown Update Kernel doesnt boot
by hvidgaard on Thursday January 11, 2018 @02:21AM
(#16122032)
It's still "only" 1.7gb/hour. If programs follow reasonable security practices, it shouldn't be possible to stumble upon secrets in the memory. This underlines the importance of things such as ASLR and not holding your key in memory longer than needed and rotating them as well.
Re:Meltdown Update Kernel doesnt boot
by AstralStorm on Thursday January 11, 2018 @04:01AM
(#16122379)
Once you know the location, if the process is not randomized, you can extract from that location. You may assume some things about implementation (e.g. libstdc++ or libc++, glibc memory allocator, general compiler version)
Additionally some hardening methods like stack protector make stack allocated objects stand out a lot from register values.
Meltdown is fast enough to learn everything about layout of data structures in kernel or other programs and then use it to extract information from particular areas holding the keys.
I suppose if there was an exploit targeted at a specific program, it would be possible to work out what location the secrets are stored in?