Aki Helin

First part done. Hash function can be selected with -H, and sha256 is converted internally to suitable 3-byte chunks for storing in hash tree, so the old checksum store can...

Hi, You are probably thinking about a scenario where the linked radamsa would constantly get something to mutate? Supporting that kind of use is something I've been planning to add...

Grr seems to use a fun approach. The only issue I have with it, is that when you run radamsa once for each output it doesn't get a chance to...

The last one is probably the correct solution. Owl should have some builtin support for building programs to be used as libraries in other C-programs. Then it would be possible...

Current plan: radamsa (and owl programs in general) work by decoding the program to run from a fasl image, encode the command line parameters as a corresponding lisp object, run...

That would end up working without radamsa-specific modifications in the planned solution, because you'd initially boot up the embedded radamsa anyway with a fake command line, on which you can...

https://github.com/aoh/owl-lisp/issues/15 is waiting for spare time. I got DoS'd by various kinds of extra work in December.

Oh, by the way, https://github.com/aoh/ni might be of interest here. It's a quick port of some radamsa-mutations to C, which should be easy to embed.

In both cases yes, though not by much. Some mutations are only possible if radamsa has had a chance to look at another file, or the same file from a...

In both cases you could generate a bunch of files and serve them as they are needed. Something like ``` # make a file for fuzzed files if necessary mkdir...