Announcement

Collapse
No announcement yet.

Nebulet: A Rust Microkernel Running WebAssembly In Ring 0

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Written by Michael Larabel in Mozilla
    While the idea of running WebAssembly in ring 0 may cause security shivers, *Mozilla* at least believes it can be done safely
    How is Nebulet related to Mozilla? Yes it is written in the language made by Mozilla but besides that I don't see any connection.

    Comment


    • #12
      No software is ever bug free, doing this in manner that is 100% safe is pipe dream. Even if it was not why risk it? Just keep loserspace code in its place.

      Comment


      • #13
        Originally posted by speculatrix View Post


        Intel, Power and Arm processors are all affected by meltdown.
        No, you're confusing them.

        "GPZ Variant 3 (Meltdown) does not apply to AMD because of our processor design. "


        Comment


        • #14
          Originally posted by speculatrix View Post
          Intel, Power and Arm processors are all affected by meltdown.
          you are confusing meltdown, which affects only intel cpus, with spectre, which affects almost every cpu that does speculative execution

          Comment


          • #15
            Originally posted by Szzz View Post
            How is Nebulet related to Mozilla? Yes it is written in the language made by Mozilla but besides that I don't see any connection.
            Please read the article again

            Originally posted by phoronix
            While the idea of running WebAssembly in ring 0 may cause security shivers, Mozilla at least believes it can be done safely if the WebAssembly is verified as well as taking optimization steps to ensure no reading/writing outside of its assigned linear memory. Other steps/optimizations are also taken to reduce possible vulnerabilities.

            Comment


            • #16
              Originally posted by LubosD View Post
              Because there is no userspace in this project.
              so to be exploited spectre is sufficient and it doesn't need meltdown too

              Comment


              • #17
                Originally posted by GunpowaderGuy View Post
                metldown proved that hatdware memory protection in some cpus ( not amd but not only intel either ) is faulty , this os is not affected because it does not uses that feature
                Well, in the same sense that a motorcycles doesn't suffer from failed seat belts and air bugs... Sure.

                Comment


                • #18
                  Can someone explain to me why this is only possible with WebAssembly? If I understand it correctly, the WebAssembly language itself does not support reading or writing to memory locations that are not assigned to the application. If that's true, then programs would not have to be checked, because they are safe by design. But the GitHub repo says the WebAssembly code is still verified. Why? And:
                  - is WebAssembly seriously the first language to provide this safety?
                  - does this mean that on a computer running this kernel, the only native program will be the kernel itself, and the rest has to be written in WebAssembly, or interpreted by a program written in WebAssembly?

                  Comment


                  • #19
                    Originally posted by GunpowaderGuy View Post
                    This should be inmune to meltdown by default , how much performance do the orher vulnerabilities cost un Intel ? And in AMD ?
                    It's immune in the sense that malware would not need to use Meltdown to break havok.
                    It's not better by any means lol.

                    Comment


                    • #20
                      Originally posted by FastCode View Post
                      Has threading and verifies if it accesses the memory region intended for it.
                      Show me this magic, I need it in my ring 3 code.
                      In safe Rust, memory can't be shared, mutable and concurrent all at the same time (it can be shared + mutable, mutable + concurrent or concurrent + shared, but this is safe).

                      Comment

                      Working...
                      X