News for hackers. Stuff that matters.
Re:Sparta: High-Performance Static Code Analyzers Based on A... by int3 on Wednesday February 20, 2019 @07:20PM (#19213388)
For a bit more context, see this blogpost we made: https://code.fb.com/open-source/sparta/
Re:Sparta: High-Performance Static Code Analyzers Based on A... by saagarjha on Wednesday February 20, 2019 @08:21PM (#19213711)
What kinds of domains do you use when you run this on dex files?
Re:Sparta: High-Performance Static Code Analyzers Based on A... by int3 on Wednesday February 20, 2019 @08:45PM (#19213844)
Re:Sparta: High-Performance Static Code Analyzers Based on A... by daoxid on Thursday February 21, 2019 @04:52AM (#19215757)
I haven't really looked into it, but how does Sparta compare to Ikos (https://ti.arc.nasa.gov/opensource/ikos/)?
Re:Sparta: High-Performance Static Code Analyzers Based on A... by cofibered on Thursday February 21, 2019 @05:31AM (#19215873)
IKOS has been originally designed to perform formal verification of embedded software and is heavily skewed toward numerical abstractions (intervals, octagons, interleaved widening/narrowing fixpoint iterator, etc.), which are computationally expensive. Since the goal is to verify critical pieces of software, it's OK to have an analysis take several hours to complete. Using IKOS also requires a deeper understanding of the theory Abstract Interpretation.

SPARTA has been designed with different goals in mind: speed and ease of use. The API is more streamlined and one can implement an analysis with minimal background in Abstract Interpretation. The algorithms in SPARTA have also been fine-tuned for maximum performance. SPARTA is meant to be used in compilers and optimizers, where speed of execution is critical.

Re:Sparta: High-Performance Static Code Analyzers Based on A... by Darmani on Thursday February 21, 2019 @03:41AM (#19215451)
This is really confusing.

There's another static analysis engine....also for Android....also called SPARTA!

https://types.cs.washington.edu/sparta/

Re:Sparta: High-Performance Static Code Analyzers Based on A... by TACIXAT on Wednesday February 20, 2019 @09:01PM (#19213913)
Disclaimer, I'm on my phone so I haven't dug into the source yet.

How is this used? For an unimplemented language, would I be coming up with how that language's instructions map into Sparta rules?

Anyhow, this looks awesome.

Re:Sparta: High-Performance Static Code Analyzers Based on A... by TACIXAT on Friday February 22, 2019 @02:33AM (#19223755)
For anyone who comes across this in the future, this is a good way to understand the terms of abstract interpretation without getting a PhD.

https://wiki.mozilla.org/Abstract_Interpretation

Re:Sparta: High-Performance Static Code Analyzers Based on A... by sanxiyn on Wednesday February 20, 2019 @11:11PM (#19214471)
Yes, writing transfer functions for dataflow analysis is your responsibility.
Re:Sparta: High-Performance Static Code Analyzers Based on A... by pltnr on Thursday February 21, 2019 @12:51AM (#19214851)
what languages does it support out of box? Or is it just a backend engine?
Re:Sparta: High-Performance Static Code Analyzers Based on A... by int3 on Thursday February 21, 2019 @01:31AM (#19214975)
It's a backend engine; it doesn't support languages out-of-the-box. That said, it's extensively used by the open-source Android bytecode optimizer [Redex](https://github.com/facebook/redex), so there's code readily available if you want to do Android bytecode analysis with SPARTA.