Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Conversation

Notices

  1. bitey cat bite bite bite bite (cybermeow@cybre.space)'s status on Tuesday, 09-Jan-2018 22:55:11 EST bitey cat bite bite bite bite bitey cat bite bite bite bite

    what I understand about spectre:
    Branch prediction isnt always right and you can trick the processor into executing a bad branch.

    What I dont understand about spectre:
    How this can get around privilege constraints like User privilege and read kernel memory and other serious things.

    In conversation Tuesday, 09-Jan-2018 22:55:11 EST from cybre.space permalink
    1. Canageek (canageek@cybre.space)'s status on Tuesday, 09-Jan-2018 23:39:32 EST Canageek Canageek
      in reply to

      @cybermeow From https://twitter.com/gsuberland/status/948907452786933762 So you make two arrays in memory. Now pick memory you aren't allowed to read: if that bit is a one, read what is in array one. If it is a 0, read what is in array two. Now, it will stop you from getting these results, but it will do this before it realizes it. But now it has either a value from array1 or array2 in cache. We are allowed to read those, so get the CPU to do that and see which answer arrives faster. That tells you if the memory you can't read is 0 or 1.

      In conversation Tuesday, 09-Jan-2018 23:39:32 EST from cybre.space permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.