Ronan Kervella

It's an opened issue, I already assigned myself on it. Now I'll work on it when I find the time. A short reminder that this project is open source, feel...

Looks like it's restriction in the Donut loader: https://github.dev/TheWover/donut/blob/dafea1702ce2e71d5139c4d583627f7ee740f3ae/include/donut.h#L430 `DONUT_MAXNAME` is set to 256. We probably need to fork https://github.com/binject/go-donut and update the loader to fix that.

> I just found out that using the "inline-execute-assembly" option allows to circumvent the problem:  > > PS: data shown on the screenshot are from an internal lab, no...

Closing as "wontfix" since it's kinda out of our control (a limitation of a dependency we use, Donut). We have alternatives which are: - the `inline-execute-assembly` extension - the incoming...

Yes, I'll document it in the wiki too.

@omnitheon is this only on the HTTP transport? If so, you can disable the OTP verification with `--disable-otp` in the listener command like this: ``` http --disable-otp ```

My understanding is you can't have OTP if there's too much desynchronization between the sliver server and the target host running the implant. So your two solutions are to either...

Yeah that's a known "bug", I need to look on how to support that.

Ok looks like we just need to implement the `BeaconOutput` function as a Go callback and wire it to the implant handler.

@moloch-- wasn't the plan to ditch CGO and use the pure Go implementation of sqlite? That would solve this kind of problems methinks.