sw33tLie

Hi there, I believe this is related to your machine config. You can either: - reduce concurrency on bbscope - increase file descriptors (ulimit -n flag) Hope this helps :)

Hey @ipk1 , I actually have released a fix yesterday for this. Can you please test the latest version and tell me if you still notice that? Thanks!

Hmm, that's weird, works here and also works for a few friends I asked to try it. Sorry to say this again but just to be 100% sure, are you...

Hi there, thanks for raising this issue. You're right, and yes it's because of the different formatting of the scope (honestly, I blame HackerOne for this :upside_down_face: ). A while...

Hi there, I took a closer look and figured out what's actually wrong. Using the --proxy flag to send all requests through Burp I saw this: ``` {"node":{"id":"Z2lkOi8vaGFja2Vyb25lL1N0cnVjdHVyZWRTY29wZS80MDQxOA==","asset_type":"OTHER","asset_identifier":"Ext. A Scope","rendered_instruction":"\u003cp\u003eProductivity,...

I think it's a great idea, and it's something I thought about before...will add it shortly :)

Hey there, thank you for raising this issue. I will take a look at the code as soon as I have time and hopefully push a fix soon..shouldn't be hard...

Hi there, we just pushed a fix for this issue. I suppose you were attempting a `fleex build` and you were using Linode. Please update fleex by running `GO111MODULE=on go...

Hey thanks for the new details. Just to make sure, you have put your token again in `~/fleex/config.yaml` and adjusted the other values according to your needs, right?

Oh yes, absolutely. JSON => XML would be dope for testing XXE also!