--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/zaproxy-develop/87db247b-731c-4b53-b0f5-ee0f09b810c6%40googlegroups.com.
So it would be a very generic 'dumb' service, all of the logic would be in the patterns.
We would then need to change ZAP to poll this service and raise alerts for any of the patterns that are discovered.
To be honest this doesnt sound that hard ;)
OK, I'm sure theres plenty more that could be done, but I think that would provide a lot of useful functionality.
I also dont think it really matters what the service is written in, although ideally it would run on as many systems as possible. So along with Java, Python and Go are possibilities (as are many others I'm sure).
What does everyone else think about this 'fag packet' design?
Does anyone know of an existing open source project that does this (and _just_ this)?
Sushil - does this sound like something you could take on?
We could definitely help with the ZAP part, that should be even easier than the service (for us).
Cheers,
Simon