thc202
thc202
You can remove that argument (assuming it's not causing the issue).
https://github.com/zaproxy/zaproxy/issues/7457#issuecomment-1246645784 If the issue is reproducible running from the command line (https://github.com/zaproxy/zaproxy/issues/7457#issuecomment-1245272429) it's not necessary to have ZAP in the equation, right? Or I misunderstood the comment… https://github.com/zaproxy/zaproxy/issues/7457#issuecomment-1246628776 You can...
To be precise you need to change the rule `rules.domxss.browserid`, more details in https://www.zaproxy.org/docs/desktop/addons/dom-xss-active-scan-rule/
@iMinusMinus ping.
I believe that's a (new) GitHub placeholder user, the issue is unassigned automatically when the user is zaproxy (old issues migrated from Google Code). @psiinon would we be able to...
@ArkaprabhaChakraborty this one.
Could you provide the steps to reproduce the issue? The scan rule [Weak Authentication Method](https://www.zaproxy.org/docs/alerts/10105/) does detect that case.
Yes, but first we need to discuss how we want this to work taking into account #4388 (which is already being worked on, in #4398), there's a great overlap between...
@setzamora with ` same UI` I was suggesting using the same UI class not use just one options panel for all, sorry for not being clear. Otherwise looks good.
This should be done in the add-on now, located in the `zap-extensions` repo.