LCBH
> btw: I found a waaay better method to instrument the PUTs without direcly modifying the source code of OpenSSL/LibreSSL. Nice. Does that correspond to what you have implemented in...
> Its still put dependant, but abstractions could be built in rust which simplify the instrumentation OK I like it. I can now use this to check matching conversation (based...
> > * Trace length varies between 8.2 and 8.6. That is weird, I would expect a lot more variance ! > > What are you refering to here? This...
> > Use state-of-the-art generation algorithms > In which area of the fuzzer would that make sense? Where generation is used. I just suggest using more advanced techniques. > >...
> `server DDoS` is kind of already included because we have a timeout in LibAFL which detects very long traces I see, with a client attacker. Alright!
Regarding claims: I think we need to keep claims somehow (for the Objective Oracle). Maybe you meant that the approach to implement claims as done in `tlspuffin-claims` will no longer...
Regarding the diagram: shouldn't the Wolfssl/OpenSSL bindings be removed?
# Milestones Step 1: - [x] write C interface for `put::Put` (without claims for now, so without the feature flag "claims") - [x] write C bindings around OpenSSL that implements...
See the results of investigations in #293 .
looks like the link is broken