Jannik Hollenbach
Jannik Hollenbach
Tested this again some more came to the following sad conclusion: libxml2-wasm doesn't work for us as the wasm sandbox is too secure. (Sad for JuiceShop, great news for everyone...
Cool idea :) It wouldn't need to solve the challenge. We already have a exclusion for requests with a Prometheus user agent. https://github.com/juice-shop/juice-shop/blob/master/routes/metrics.ts#L70
Added a "plain" implementation" for it in 621d609d61234fd9e7889d4b07543d96d9b1686e :) Will be coming with the next release, which should be out soon :) Persisting the total cheat score when a challenge...
Hi @cnsino thanks for ht edetailed report. I've never seen this behaviour and I'm running thousands of scans daily, so I'm guessing there is something with your setup which is...
I think i've now also observed the same behaviour, didn't se it before because the job retries made the parser succeed in the end. But it were just two cases...
Could this be a good project for GSoC? Sounds like a nice isolated project a student could work on.
wouldn't recommend this particular issue as this needs a breaking change release which we aren't planning to do for some months
We've delayed this long enough :D We've been checking off all boxes for a while :) I've submitted the request for promotion 🤞🤞🤞
The requirement for project maturity levels are here: https://owasp.org/www-committee-project/
Probably broken due to this Update: https://github.com/secureCodeBox/secureCodeBox/pull/3390