[owasp_seraphimdroid_project] GitHub created

Nikola Milosevic nikola.milosevic at owasp.org
Sun Sep 8 09:02:58 UTC 2013

Thank you for the contribution. I think that this will be good. Just one
question. What happens if user dials the number that is not known? Will it
be also blocked and user notified?

I think that SQLite will be good. I wanted to created log logic, with table
in SQLite, but until now I had no time. Maybe I will manage later today or
next weekend.

I also want to announce that we will be presenting our project on Software
Freedom day in Belgrade this year. It will be Saturday September 21st in
O3one gallery. Aleksandar would you like to come, and say couple of words?

Pozdrav/Best regards,

Nikola Milošević
Serbian local chapter leader
nikola.milosevic at owasp.org
OWASP - Open Web Application Security
OWASP Serbian Local Chapter <https://www.owasp.org/index.php/Serbia>

On Sun, Sep 8, 2013 at 10:40 AM, Aleksandar Abu-Samra <
aleksandar at abu-samra.com> wrote:

> Hello all,
> I have just pushed some prototype code on outgoing calls interception<https://github.com/nikolamilosevic86/owasp-seraphimdroid/tree/master/Seraphimdroid/src/org/owasp/seraphimdroid/outgoingcalls>
> .
> Here are some short notes:
>    - We cannot know what application, stock or other, made a call request
>    (please correct me if I am wrong), so we must treat every call equally
>       - Therefore, distinction could be made by looking at call's country
>       code or searching for the number in user's contact list
>       - I've implemented the latter, blocking any unknown numbers and
>       raising a notification. After selecting the notification, user is presented
>       with call log (not yet there), with an option to redial blocked calls.
>       - Any other idea?
>       - We should decide if it is better to make distinct or unifying
>    logging class. Also, should we use SQLite or file as a database?
>    - I'm testing everything on 4.3 Android so I'm not sure how everything
>    responds on earlier versions.
> That's it for now,
> Cheers
> _______________________________________________
> Owasp_seraphimdroid_project mailing list
> Owasp_seraphimdroid_project at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp_seraphimdroid_project
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp_seraphimdroid_project/attachments/20130908/1fcc1c00/attachment.html>

More information about the Owasp_seraphimdroid_project mailing list