Dan Gohman

@Sunfishcode

Focused on WebAssembly, WASI, Wasm-native I/O, LLVM Wasm support, WASI libc, Wasmtime, cap-std, Cranelift.

Uniuse en agosto de 2014
2 Fotos ou vídeos Fotos e vídeos

Chíos

Bloqueaches a @Sunfishcode

Estás seguro de que queres ver estes chíos? Ver os chíos non desbloqueará a @Sunfishcode

  1. 2 de set.

    New blog post: What should safety in Rust protect against?

    1 rechouchío 12 gústames
    Desfacer
  2. rechouchiou
    30 de ago.

    also starting to switch over our codebase to `cap-std::fs` from & for explicit capability-based security of I/O, it's great! once done will be able to be enforced, in our crates, with this lint also and a giant Clippy.toml:

    1 resposta 3 rechouchíos 23 gústames
    Amosar este fío
    Amosar este fío
    Desfacer
  3. 27 de ago.

    Tide modified to run on cap-async-std: when serving static directories, it ensures that no paths escape those directories, even via symlinks. The diff is nice and simple:

    6 gústames
    Desfacer
  4. 21 de ago.

    I/O safety is now in Rust Nightly!

    10 rechouchíos 67 gústames
    Desfacer
  5. 10 de ago.

    #8 in the 2021 CWE Top 25 Most Dangerous Software Weaknesses is "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')". cap-std can help protect Rust programs.

    4 gústames
    Desfacer
  6. rechouchiou
    25 de xul.

    I disagree. We still haven't succeeded in making memory safety considered a base foundation. People are still making new languages that aren't memory safe, and they're getting popular.

    memory safety is not a big deal in the same sense that not dying from the black plague is not a big deal—you're probably going to have a hard time producing great works if it's a problem left unsolved, but it's also mere foundation
    Amosar este fío
    10 respostas 19 rechouchíos 152 gústames
    Desfacer
  7. 14 de xul.

    Want to scan a Rust codebase for uses of dynamic file paths, with the ability to mark file paths that are constants as ignored? I put together a little utility:

    4 gústames
    Desfacer
  8. 13 de xul.

    New blog post: I/O safety and speed: Why not both? The I/O safety RFC is now merged; here's a first look at how it works in practice.

    7 rechouchíos 16 gústames
    Desfacer
  9. rechouchiou
    12 de xul.

    now has an accepted RFC for I/O Safety, to handle the lifetimes of file descriptors (on UNIX) and OS handles and sockets (on Windows): This will make it possible to write safe functions that operate on these underlying OS objects.

    4 respostas 42 rechouchíos 261 gústames
    Amosar este fío
    Amosar este fío
    Desfacer
  10. 14 de xuño

    New blog post: Introducing cap-std, a Capability-based version of the Rust standard library: With cap-std in use in Wasmtime, the API no longer using unsafe, and new cap_std::net support, this is a good time to check it out!

    7 rechouchíos 24 gústames
    Desfacer
  11. rechouchiou
    9 de xuño

    Wasmtime 0.28.0 is out! 🎉 This release contains the Rust API refactoring that solves the !Send issue for Wasmtime store-related objects. It's a breaking change, but one that makes the API safer and also much easier to use in async contexts.

    1 resposta 4 rechouchíos 31 gústames
    Amosar este fío
    Amosar este fío
    Desfacer
  12. 3 de xuño

    The plot twist with `OwnedFd` and `BorrowedFd` is `repr(transparent)`, so I/O safety can extend all the way to the FFI boundary. It could theoretically extend all the way to a `syscall` in asm in the future.

    5 gústames
    Desfacer
  13. 2 de xuño

    I built a prototype of an OwnedFd and BorrowedFd API Rust, for the I/O safety RFC discussion:

    1 resposta 1 rechouchío 14 gústames
    Desfacer
  14. rechouchiou
    2 de xuño

    After years of perf optimizations, JS is running way faster in the browser Today, we're starting work to optimize JS perf in places where different rules apply, like Serverless and iOS devices And this is possible because of WebAssembly 🚀

    18 respostas 245 rechouchíos 1.025 gústames
    Amosar este fío
    Amosar este fío
    Desfacer
  15. 25 de maio

    My RFC proposing I/O safety for Rust is now posted!

    16 gústames
    Desfacer
  16. rechouchiou
    28 de abr.

    WASI, interface types, module linking, and IO streams/arrays are crucial ingredients for on the cloud (and everywhere). I am so excited to be part of this community. Congrats to the

    2 rechouchíos 13 gústames
    Desfacer
  17. rechouchiou
    28 de abr.

    I'm super excited for to join the effort to build a secure software ecosystem using !

    4 rechouchíos 45 gústames
    Desfacer
  18. rechouchiou
    28 de abr.

    Thrilled to join , , and in welcoming , , , , , and to the Bytecode Alliance. It's exciting to have such a capable coalition come together to lay the groundwork for a more secure software ecosystem.

    Today, joins Fastly, Intel, and Microsoft in announcing the incorporation and expansion of the Bytecode Alliance, a cross-industry partnership to advance a vision for fast, secure, and simplified software development based on .
    4 rechouchíos 29 gústames
    Desfacer
  19. rechouchiou
    28 de abr.

    🥳 Huge congratulations to the for officially becoming a foundation today! 🎊 We here at DeisLabs are proud users and contributors to the foundation's projects and look forward to what's to come:

    11 rechouchíos 17 gústames
    Desfacer
  20. rechouchiou
    28 de abr.

    1/ Today, the is the first blockchain to join Mozilla, Microsoft, Intel and other collaborators as a member of the Bytecode Alliance.

    13 respostas 228 rechouchíos 625 gústames
    Amosar este fío
    Amosar este fío
    Desfacer

@Sunfishcode aínda non chiou.

Parece que a carga tarda un chisco

É posible que o Twitter estea por riba da súa capacidade ou teña un impo momentáneo. Téntao de novo ou visita o Estado do Twitter para obter máis información.

    Tamén che pode gustar

    ·