Closed lrubasze closed 11 months ago
Hello Lukasz!
We also uncovered the bug after deploying ziggy-v0.7.0 last week, and are working on a fix.
Our temporary patch is to use the --no-honggfuzz
flag to only use AFL++ fuzzing.
Yeah, using this flag too :)
Is there some ziggy
version, which is not affected?
Anything before 0.7.0
should work with honggfuzz, but there are many cool changes in 0.7.0
, so we are using it anyways until the bug is fixed.
True, changes are really impressive. Cannot wait to have it working with honggfuzz! Good luck :)
this has nothing to do with ziggy but is a bug in honggfuzz that is apparently difficult to fix. this is due some weird side effect of an unknown package or version that is installed on (older) Debian/Ubuntu it seems.
Fixed with https://github.com/srlabs/ziggy/commit/57a12927d87127faf51759dab540d3bc81446494 in 0.7.1
, which I just published.
Make sure to cargo install ziggy
and update the version in your Cargo.toml
:singer:
That was quick! Works like a charm on Ubuntu. Thanks 👏
Hi, trying to play a bit with
ziggy
, but unfortunately encountered an issue when buildingziggy-honggfuzz v0.5.55
.I am using
Ubuntu 20.04.6
ziggy repo commit:0b49b7bdbd482693f1dfa2eeab5a8a348ad56765
Followed an example from this READMEAnd the last step fails producing below log:
Could you please advise how to fix this problem?