You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Giorgio Zoppi (Jira)" <ji...@apache.org> on 2020/05/10 12:43:00 UTC
[jira] [Comment Edited] (FINERACT-969) Run OWASP zaproxy.org
against Fineract (e.g. fineract.dev)
[ https://issues.apache.org/jira/browse/FINERACT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103775#comment-17103775 ]
Giorgio Zoppi edited comment on FINERACT-969 at 5/10/20, 12:42 PM:
-------------------------------------------------------------------
Ok, as attacker i will use a EC2 instance on my domain enlista4u.com toward your fineract.dev. I am going to do now.
was (Author: giorgio):
Ok, as attacker i will use a EC2 instance on my domain enlista4u.com toward your fineract.dev
> Run OWASP zaproxy.org against Fineract (e.g. fineract.dev)
> ----------------------------------------------------------
>
> Key: FINERACT-969
> URL: https://issues.apache.org/jira/browse/FINERACT-969
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Security
> Reporter: Michael Vorburger
> Assignee: Giorgio Zoppi
> Priority: Major
>
> [~giorgio] in FINERACT-853 suggested to run [https://www.zaproxy.org|https://www.zaproxy.org] against Fineract.
> That sounds like a Great Idea - and may yield some interesting results and holes worth plugging.
> I this is easier to do against a public server instead of locally, then I hereby offer https://www.fineract.dev for this purpose. As its FAQ says, quote: _"Try to crash our demo - and if you manage, then work with us in the open source project to make the Fineract code more scaleable and reliable!"_ :D
--
This message was sent by Atlassian Jira
(v8.3.4#803005)