AdamKorcz

That is strange given that Kubeedge builds fine on OSS-Fuzz.

Instead of just removing, I suggest migrating the fuzzers upstream. I will be happy to do that over the next couple of weeks for you.

> I read all comments in prior PR, seems like everything is resolved except dependency concerns. Can you please confirm that everything is addressed? I should say so, since the...

@serathius I have minimized the dependencies. Could you have a look?

> The dependencies seem good - but now we're using what looks a lot like a fork that might one day accidentally go away, at which point the module would...

> I would wait until the change is properly upstreamed, I don't understand why after almost 3 quarters of fuzzer development ([context](https://github.com/etcd-io/etcd/pull/14674#issue-1432183707)) we decide to cut corners now. > >...

Changed to the upstream `go-fuzz-headers`. Please review again.

> Unfortunately it feels like we would basically need to have our own implementation of [mojo-executor](https://github.com/mojo-executor/mojo-executor) if we actually want to harden this and not rely on the argument splitting...