Ronan Kervella

Wow that's great, thanks @freefirex . From what I've seen there's a couple of other BOFs that are probably affected (`nslookup`, `adcs_enum` ...) , so fixing the loader will make...

Awesome I'll merge that now. Thanks !

@r00t0v3rr1d3 it should be fixed now. Just run `armory update` to get the new loader version and everything should work.

Yeah I suspect something about a malformed extension manifest, I'll have a look.

@r00t0v3rr1d3 I can't reproduce the crash for `sa-uptime`, are you sure you're up to date? : ```shell [server] sliver (EMPTY_JUDGMENT) > armory install sa-uptime [*] Installing extension 'sa-uptime' (v0.0.14) ......

Ah I only tested in session mode, there could be quirks in beacon mode indeed.

> I’ve also been consistently getting no output the first time any coffloader related extension is run. So after the initial beacon comes in, run something like sa-ipconfig. Get no...

Neat I'll run some tests in beacon mode then.

Weird for uptime as it doesn't take any parameters (resources shouldn't either, I just checked).

It's probably due to a timeout on the first forwarded TCP connection, we could probably set a lower timeout than the gRPC default timeout.