kobebrookskC3

6 ms·

31.
by kobebrookskC3 1y ago
> Oberon is similar. The typesolver will determine if something is safe, without the need for explicitly borrowing anything. so what does oberon do to prevent you from resizing a possibly reallocating array while holding a reference into
32.
by kobebrookskC3 1y ago
doesn't spark do something inspired by rust to get safe dynamic memory allocation? https://docs.adacore.com/spark2014-docs/html/ug/en/source/ac... what does oberon do?
33.
by kobebrookskC3 1y ago
sure, rust is not the final answer to eliminating memory safety bugs from systems programming. but what are the alternatives, that aren't even more onerous and/or limited in scope (ats, frama-c, proofs)?
34.
by kobebrookskC3 1y ago
i bet 99% of people will wash out of the 30 day routine, me being one of them. there are better ways to start than drinking from the firehose of "simple anime"
35.
by kobebrookskC3 1y ago
in practice, i don't see rust programs with memory unsafety, but i picked the first zig project that came to mind, bun, and it is riddled with segfaults https://github.com/oven-sh/bun/issues?q=is%3Aissue%20sta
36.
by kobebrookskC3 2y ago
even in c, you can't assume memory is a flat array of bytes. pointers have provenance, and compilers exploit this: https://godbolt.org/z/ondGh4Ynn
37.
by kobebrookskC3 2y ago
does making software scale? i see exploits for android/ios even though they spend millions if not billions on securing it. which unsound techniques make exploits unfeasible? i'm not even looking for a guarantee, just an absence in
38.
by kobebrookskC3 2y ago
what vulnerabilities does rust introduce over c/c++?
39.
by kobebrookskC3 2y ago
some correctness matters more than others. for a web browser, i would rather use a browser that is buggy/janky/crashy but doesn't give random websites arbitrary native code execution over a browser that is logically correct e
40.
by kobebrookskC3 2y ago
how does zig express a trait like Send https://doc.rust-lang.org/std/marker/trait.Send.html which ensures that values can safely be moved to another thread, for example when spawning a thread? https://d
41.
by kobebrookskC3 2y ago
no, undefined behavior not just behavior that is not covered by the language definition. undefined behavior is term of art largely taken from C/C++, basically meaning that correct programs are assumed not to have these behaviors. for e
42.
by kobebrookskC3 2y ago
you wanna verify all your c just for memory safety? i bet you if you actually tried to verify c for memory safety, you would come screaming back to rust. and also seL4 is about 10k lines of code, designed around verification, sequential, an
43.
by kobebrookskC3 2y ago
modules are meant to be the boundary for a safe abstraction, but sometimes you get fun holes like https://github.com/rust-lang/rust/issues/128872 where you can implement Copy for a type in a different module
44.
by kobebrookskC3 2y ago
seems pretty safe in practice https://security.googleblog.com/2024/09/eliminating-memory-s...
45.
by kobebrookskC3 2y ago
> If people really cared about that above all else they would use a memory-safe language, which Rust is not, such as Java or Python or Haskell or something. people already use languages like java or python or js in most cases! it's
46.
by kobebrookskC3 2y ago
all those advantages and disadvantages you list are basically insignificant compared to rust being memory safe by default and c/c++ not. governments aren't bugging projects about any of those, but are about memory safety.
47.
by kobebrookskC3 2y ago
why not? just tell them "if you don't like it, you can get a refund" (aka fuck off)
48.
by kobebrookskC3 3y ago
how is integer overflow unsafe? integer overflow in rust is not ub, unless you opt into the *_unchecked methods
49.
by kobebrookskC3 4y ago
it's also a very limited version of C, without concurrency, dynamic memory allocation, or goto, and you can't even take the address of local variables!
50.
by kobebrookskC3 4y ago
curiously, seL4 doesn't need to trust the compiler: the assembly is verified to satisfy the abstract specification
51.
by kobebrookskC3 4y ago
if you see it in the logs, that seems like bots looking for low hanging fruit. what about focused attacks by sophisticated adversaries? here, a heap buffer overflow in a c++ library is a major part of enabling rce https://en.wiki
52.
by kobebrookskC3 4y ago
is your software actively attacked like major browsers/operating systems?
53.
by kobebrookskC3 4y ago
https://github.com/seL4/seL4 begs to differ :)
54.
by kobebrookskC3 4y ago
maybe https://docs.rs/cap-std/latest/cap_std/fs/index.html would prevent that?
55.
by kobebrookskC3 4y ago
> Rust ... "Isn't Really Safe" because you can get into a point where memory is corrupted i dare you to find memory corruption in safe rust that isn't already on an issue tracker. > Saying that a language is either
56.
by kobebrookskC3 5y ago
what do you mean invalidated? the point of proofs is that they will be still be as true today as they will millenia into the future. pythagoras' theorem is just as true today as it was millenia ago.
57.
by kobebrookskC3 5y ago
the world can't afford new code written in a blatantly memory-unsafe language
58.
by kobebrookskC3 5y ago
> it doesn't solve any problem they have you mean a problem blithely ignored until the software becomes important enough to attack, at which point, it's too late to rewrite the "very old" code? https://goog
59.
by kobebrookskC3 5y ago
supposing a compiler, was written in c, would frama-c be able to get similar guarantees that coq allows for compcert? also, what happens when the loop invariants can't be automatically proved? is there some way to manually prove invari
60.
by kobebrookskC3 5y ago
these are relatively small, relatively self-contained algorithms and data structures though, right? not a "big" piece of software.

More ›