Viewing profile — mwhicks1
mwhicks1
HN member- Joined
- Wed, Jul 01, 2015, 6:02 PM UTC
- HN karma
- 47
- Public activity
- 17 items
- HN profile
- View on Hacker News ↗
About mwhicks1
No profile information was provided.
Recent public activity
-
comment
Comment #34092930
> 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
-
comment
Comment #26013266
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 Che…
- story
- story
-
comment
Comment #18689885
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
-
comment
Comment #17925362
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.
-
comment
Comment #17925354
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 …
-
comment
Comment #17925340
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-enthusi…
- story
-
comment
Comment #11016061
Some good discussion points on the blog comments about forgotten invention of software security ideas.
- story
-
comment
Comment #9818725
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 si…
-
comment
Comment #9818721
Yes, memory mappings should be preserved, so I can't immediately think why it wouldn't work.
-
comment
Comment #9818718
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 …
-
comment
Comment #9813906
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 …
-
comment
Comment #9813899
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.
-
comment
Comment #9813877
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 a…