mwhicks1

5 ms·

1.
by mwhicks1 4y ago
> The breakthrough will come when someone can create an automated system to convert unsafe C into safe something https://dl.acm.org/doi/abs/10.1145/3527322
2.
by mwhicks1 6y ago
At Correct Computation ( https://correctcomputation.com/ , we are hiring), we are developing a tool called 3C to provide automation assistance for the conversion of C code into Checked C. A completely automated approach is im
3.
A Small Matter of Programming(blog.sigplan.org)
1 points by mwhicks1 7y ago|0 comments
4.
How to Have Real World Impact, in Five Easy Pieces(blog.sigplan.org)
41 points by mwhicks1 7y ago|3 comments
5.
by mwhicks1 8y ago
Hopefully soon, “moving in that direction” can be done by slowly porting to Checked C, while always retaining an executable artifact. https://github.com/Microsoft/checkedc
6.
by mwhicks1 8y ago
Note that some papers do come close to meeting what we view is the right standard. Table 1 shows that T-Fuzz does pretty well, for example.
7.
by mwhicks1 8y ago
The last comment is not justified by the paper. The paper shows one case where the dumb thing finds tons of crashes, but several other cases in the same figure where it finds zero crashes. And the figure there is just one target program. Mo
8.
by mwhicks1 8y ago
I'm one of the authors of the paper. Two quick things I want to say: I've written a blog post that is a short but rigorous description of the paper's results: http://www.pl-enthusiast.net/2018/08/23&
9.
Confluences in Programming Languages Research(pl-enthusiast.net)
2 points by mwhicks1 10y ago|0 comments
10.
by mwhicks1 11y ago
Some good discussion points on the blog comments about forgotten invention of software security ideas.
11.
Interview with Facebook’s Peter O’Hearn(pl-enthusiast.net)
18 points by mwhicks1 11y ago|0 comments
12.
by mwhicks1 11y ago
You can do a lot with load balancing on web architectures, but some things remain problematic. If you read the introduction of the Kitsune paper, linked from the kitsune-dsu.com site, you'll see some argumentation about this.
13.
by mwhicks1 11y ago
Yes, memory mappings should be preserved, so I can't immediately think why it wouldn't work.
14.
by mwhicks1 11y ago
There's no need to register file descriptors, since these stay open during the upgrade -- the process identity doesn't change. As far as a fundamental difference with the approach you propose: We actually tried it with an earlier
15.
by mwhicks1 11y ago
To add: The number of changes tends to be very small, as reported in the paper. We are talking 100-300 LOC even for applications that are 100 KLOC. And these changes are robust in the sense that once you retrofit to include them, you rarely
16.
by mwhicks1 11y ago
If such states are preserved while the process that used them is still running then there is nothing to do: They will still be available to the updated program.
17.
by mwhicks1 11y ago
I was just about to point you to this paper (I'm a co-author), but you beat me to it. The JVM has a fix-and-continue updating feature that perhaps replacing method bodies as long as (a) the method is not running, and (b) it has the sam