home.social

#tockos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tockos, aggregated by home.social.

  1. It's official! will be hosted at Microsoft in Redmond, WA, just a stone's throw from @rustconf on September 5th. Join us for a schedule on in new places, verification, low-level LLVM hackery, and more!

    world.tockos.org/tockworld8/re

  2. It's official! #TockWorld8 will be hosted at Microsoft in Redmond, WA, just a stone's throw from @rustconf on September 5th. Join us for a schedule on #TockOS in new places, #Rust verification, low-level LLVM hackery, and more!

    world.tockos.org/tockworld8/re

  3. It's official! #TockWorld8 will be hosted at Microsoft in Redmond, WA, just a stone's throw from @rustconf on September 5th. Join us for a schedule on #TockOS in new places, #Rust verification, low-level LLVM hackery, and more!

    world.tockos.org/tockworld8/re

  4. It's official! #TockWorld8 will be hosted at Microsoft in Redmond, WA, just a stone's throw from @rustconf on September 5th. Join us for a schedule on #TockOS in new places, #Rust verification, low-level LLVM hackery, and more!

    world.tockos.org/tockworld8/re

  5. In Summary, Rust + Tock OS Architecture + Lightweight verification is a solution to provide safe firmware.

    #OSFC #RustLang #TockOS

  6. In Summary, Rust + Tock OS Architecture + Lightweight verification is a solution to provide safe firmware.

    #OSFC #RustLang #TockOS

  7. In Summary, Rust + Tock OS Architecture + Lightweight verification is a solution to provide safe firmware.

    #OSFC #RustLang #TockOS

  8. In Summary, Rust + Tock OS Architecture + Lightweight verification is a solution to provide safe firmware.

    #OSFC #RustLang #TockOS

  9. In Summary, Rust + Tock OS Architecture + Lightweight verification is a solution to provide safe firmware.

    #OSFC #RustLang #TockOS

  10. "An integer overflow caused $370M to vaporize in 40 seconds."

    When a rocket exploded in flight because of two simultaneous integer overflow in independently written systems.

    Luckily the industry has learned from this, right? Not really, with some Boeing planes having to be rebooted every 51 days to prevent catastrophically wrong information being shown to pilots.

    This is Samir's talk on Tock OS, or how to secure firmware at compile time.

    #OSFC #OSFC2024 #TockOS #RustLang

  11. "An integer overflow caused $370M to vaporize in 40 seconds."

    When a rocket exploded in flight because of two simultaneous integer overflow in independently written systems.

    Luckily the industry has learned from this, right? Not really, with some Boeing planes having to be rebooted every 51 days to prevent catastrophically wrong information being shown to pilots.

    This is Samir's talk on Tock OS, or how to secure firmware at compile time.

    #OSFC #OSFC2024 #TockOS #RustLang

  12. "An integer overflow caused $370M to vaporize in 40 seconds."

    When a rocket exploded in flight because of two simultaneous integer overflow in independently written systems.

    Luckily the industry has learned from this, right? Not really, with some Boeing planes having to be rebooted every 51 days to prevent catastrophically wrong information being shown to pilots.

    This is Samir's talk on Tock OS, or how to secure firmware at compile time.

    #OSFC #OSFC2024 #TockOS #RustLang

  13. "An integer overflow caused $370M to vaporize in 40 seconds."

    When a rocket exploded in flight because of two simultaneous integer overflow in independently written systems.

    Luckily the industry has learned from this, right? Not really, with some Boeing planes having to be rebooted every 51 days to prevent catastrophically wrong information being shown to pilots.

    This is Samir's talk on Tock OS, or how to secure firmware at compile time.

    #OSFC #OSFC2024 #TockOS #RustLang

  14. "An integer overflow caused $370M to vaporize in 40 seconds."

    When a rocket exploded in flight because of two simultaneous integer overflow in independently written systems.

    Luckily the industry has learned from this, right? Not really, with some Boeing planes having to be rebooted every 51 days to prevent catastrophically wrong information being shown to pilots.

    This is Samir's talk on Tock OS, or how to secure firmware at compile time.

    #OSFC #OSFC2024 #TockOS #RustLang

  15. Oh, there are now #FIDO security keys based on #Google's #OpenSK firmware for #Titan based on #TockOS (both in #Rust), available for purchase:
    shop.ftsafe.us/products/opensk

    Do note that these do *not* feature a secure element and are not resistant to more advanced physical attacks or side channels, although still probably an upgrade to disk storage as long as you keep the key safe:
    feitiantech.github.io/OpenSK_U

    Nevertheless, an interesting toy!

  16. Oh, there are now #FIDO security keys based on #Google's #OpenSK firmware for #Titan based on #TockOS (both in #Rust), available for purchase:
    shop.ftsafe.us/products/opensk

    Do note that these do *not* feature a secure element and are not resistant to more advanced physical attacks or side channels, although still probably an upgrade to disk storage as long as you keep the key safe:
    feitiantech.github.io/OpenSK_U

    Nevertheless, an interesting toy!

  17. Oh, there are now #FIDO security keys based on #Google's #OpenSK firmware for #Titan based on #TockOS (both in #Rust), available for purchase:
    shop.ftsafe.us/products/opensk

    Do note that these do *not* feature a secure element and are not resistant to more advanced physical attacks or side channels, although still probably an upgrade to disk storage as long as you keep the key safe:
    feitiantech.github.io/OpenSK_U

    Nevertheless, an interesting toy!

  18. Oh, there are now #FIDO security keys based on #Google's #OpenSK firmware for #Titan based on #TockOS (both in #Rust), available for purchase:
    shop.ftsafe.us/products/opensk

    Do note that these do *not* feature a secure element and are not resistant to more advanced physical attacks or side channels, although still probably an upgrade to disk storage as long as you keep the key safe:
    feitiantech.github.io/OpenSK_U

    Nevertheless, an interesting toy!

  19. Oh, there are now #FIDO security keys based on #Google's #OpenSK firmware for #Titan based on #TockOS (both in #Rust), available for purchase:
    shop.ftsafe.us/products/opensk

    Do note that these do *not* feature a secure element and are not resistant to more advanced physical attacks or side channels, although still probably an upgrade to disk storage as long as you keep the key safe:
    feitiantech.github.io/OpenSK_U

    Nevertheless, an interesting toy!

  20. is making progress. It's now a supported board in ! Very bare bones, but I'm working on adding drivers.

    github.com/tock/tock/pull/3182

  21. #Jazda is making #upstreaming progress. It's now a supported board in #TockOS ! Very bare bones, but I'm working on adding drivers.

    github.com/tock/tock/pull/3182

  22. #Jazda is making #upstreaming progress. It's now a supported board in #TockOS ! Very bare bones, but I'm working on adding drivers.

    github.com/tock/tock/pull/3182