Raphael Raph Carvalho

@dlenski, @mariusgrigaitis, @graphitemaster: just added the below section to README that may be interesting to you all: ``` What to do when you face this error "Unable to read /proc/kallsyms..."...

@Siprah Not in the near term, but patches are welcome though.

Windows support is also interesting BTW. Thanks for opening this issue

@dlenski actually that means it's unable to exploit meltdown. I think I need to rephrase that. Would it work if it doesn't print things like "0x0000000000000000 -> That's irq_stack_union" when...

@dlenski I'll leave this issue opened for me to reproduce it and see what I can do about it. Thanks for the report!

BTW, the output is now: ``` $ ./meltdown-checker Checking whether system is affected by Variant 3: rogue data cache load (CVE-2017-5754), a.k.a MELTDOWN ... Checking syscall table (sys_call_table) found at...

@dlenski could please check if https://github.com/paboldin/meltdown-exploit works for you? I may consider getting closer to its approach if it does.

@UnserKapitaen what's exactly the output of meltdown-exploit to you? i'll see what's wrong with the checker for some specific environments, maybe the lack of dynamic calculation of cache hit threshold....

I think we'll need to implement ideas presented here: https://gruss.cc/files/kaiser.pdf It's said that meltdown can be used to bypass KASLR, and from there, we could figure out some places in...

Very good idea @bw0x00. I'll add it to my list of things to do. I could add a run script that will guide the user through it if it finds...