[Soot-list] About Terms of Data-Flow Analysis

Bodden, Eric eric.bodden at sit.fraunhofer.de
Mon Mar 3 09:00:21 EST 2014


Hi Steven.

Side-effects would in fact be the correct term, I think. It's frequently used in the literature. The general notion of side-effect is not restricted to taint, of course, but I guess this should become clear from the context.

Eric

On 24.02.2014, at 08:12, Steven Lee <Elderry at outlook.com> wrote:

> Hello everyone, I am writing a paper about Android Security. Then it comes to a problem like this:
>  
> class A(){
>     private static int a;
>     public static void someMethod();
>     ......
> }
>  
> I use this example to show that if A.someMethod() is called somewhere, then the value of A.a may be changed, or when the method and field are not static, or there are some hierarchy problems involved in. I am going to detect this potential issue through static analysis like data-flow analysis with Soot.
>  
> Now my question is: how do I describe this in the terms of data-flow analysis or class hierarchy analysis in Soot? I am using "side-effect" and considering it an unprofessional expression. Is there a better and more formal one?
>  
> Moreover, the data-flow tutorial of Soot is confusing to me. I’m following Soot Survivors’ Guide, the part of using Soot as a standalone tool is easy to understand, however how do I use it as a data-flow frame? Should I include it in my analysis program and call some methods in it, or is there a more detailed example?
>  
> Thanks for your help!
>  
> Steven Lee
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list

--
Prof. Eric Bodden, Ph.D., http://sse.ec-spride.de/ http://bodden.de/
Head of Secure Software Engineering  at Fraunhofer SIT, TU Darmstadt and EC SPRIDE
Tel: +49 6151 16-75422    Fax: +49 6151 16-72051
Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20140303/5ad7664c/attachment-0001.bin 


More information about the Soot-list mailing list