Taras,
On Tue, Jun 19, 2012 at 12:40 PM, Taras wrote:
> Andres,
>
> Yes, I plan to spend this week coding of xss plugin:)
> My idea is to have opportunity to find out current HTML context of payload
> and determine can our XSS payload can break this context.
Perfect, that's really what we ne
Andres,
Yes, I plan to spend this week coding of xss plugin:)
My idea is to have opportunity to find out current HTML context of
payload and determine can our XSS payload can break this context.
If it can then we have possible XSS flaw.
I **hope** that number of requests to detect possible XSS f
@List: I've shared this file with Taras 3 or 4 weeks ago and we talked
face to face about it, we decided that he was going to be working on
the XSS plugin improvements and he just created a branch for it.
@Taras: Please share your progress regarding the XSS plugin with us in
the w3af-develop maili
Ervis,
On Wed, Jun 6, 2012 at 6:13 PM, Andres Riancho wrote:
> Ervis,
>
> Taras has been busy these days and he won't be able to complete
> the CSRF detection plugin for now, so I thought that you could help
> out. So, the basic setup you need to have to work on this is:
Were you able to
Taras,
On Tue, Jun 19, 2012 at 10:21 AM, Taras wrote:
> Andres, sorry for delay.
>
> Great job! How can we do QA here? Simply run w3af as usual and wait for some
> exceptions?
This was merged into trunk already :D I hope users are enjoying the
new error handling . In order to test it you can mod
Andres, sorry for delay.
Great job! How can we do QA here? Simply run w3af as usual and wait for
some exceptions?
By the way:
> w3af is officially supported under Python 2.6
for a long time I use w3af with Python 2.7 and there is no problems with
it. May be we could increase supported version
