ikos
checkedc
ikos | checkedc | |
---|---|---|
14 | 21 | |
1,986 | 3,183 | |
0.5% | 0.0% | |
7.5 | 0.0 | |
about 1 month ago | over 1 year ago | |
C++ | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ikos
- Static analyzer IKOS 3.2 Released
- Static analyzer IKOS 3.2-rc1 published – Request for testers
-
The NSA advises move to memory-safe languages
I beg to differ: there are a few tools which are comparable.
Frama-C (https://www.frama-c.com) is an open source framework that has, among its analyzers, one based on abstract interpretation (https://www.frama-c.com/fc-plugins/eva.html) that is very similar in spirit to Astree.
MOPSA (https://mopsa.lip6.fr) is another open-source project (albeit more recent, and in a more "academic" stage) that also provides abstract interpretation to analyze C programs for flaws.
NASA also released IKOS (https://github.com/NASA-SW-VnV/ikos), on the same vein.
Of course they lack the polish of a product which costs tens of thousands of euros per license, but they are open source, and their purpose is the same: to ensure code safety via formal methods, in particular abstract interpretation.
It is possible to get these tools to analyze some code and generate no complaints, which ensures absence of several kinds of problems, such as memory safety issues.
Then again, it's hard to know exactly how much they differ from Astree, since you need a license to compare them, and I don't even know if you are allowed to publish such comparisons.
-
Does anyone use IKOS for static analysis?
I've been playing around with running IKOS (https://github.com/NASA-SW-VnV/ikos), it sounds very cool but doesn't seem to be super well maintained. I've managed to compile my project to llvm bit-code and run the IKSO on it, but the actual analysis seems to be buggy. There are open issues for the problems I encountered, but the make the analysis pretty useless (it thinks most functions are unreachable).
- Astrée Static Analyzer for C and C++
-
Checked C
> https://www.absint.com/astree/index.htm
This looks interesting. It's based on abstract interpretation which is more or less the most powerful approach for imperative code available. (Because the way it works it's likely slow as hell though, I guess).
But it's closed source. One of this kind of products where you need to asks for the price… I think we all know what this means: It'll be laughably expensive.
I don't see any offer for OpenSource projects frankly.
> https://github.com/NASA-SW-VnV/ikos
Also abstract interpretation based. Looks less polished than the first one at first glance.
It's under some questionable license. According to OSI it's OpenSource. According to the FSF it's not. (The FSF argument sounds strong. They're right in my opinion. This NASA license does not look like OpenSource).
But an OpenSource project could use it for free I assume.
> https://github.com/static-analysis-engineering/CodeHawk-C
Much more constrained in scope than the other ones. But looks a little bit "too academic" imho: Uses its own C parser and such.
At least it's OpenSource under MIT license.
Thanks for the links either way! Good to know about some tools in case one would need them at some point.
> I have planned to try using them on OpenZFS for a while, but I am still busy reviewing and fixing reports made by conventional static analyzers.
Stupid question about usual C development practices (as I don't have much contact with that):
Aren't analyzers today part of the build pipeline form the get go? Especially as C is known to be full of booby traps.
Imho it shouldn't be even possible to push anything that has issues discovered by tools.
This should be the lowest barrier as most code analyzers are at most able to spot quite obvious problems (the commercial one above is likely an exception to this "rule"). When even the usual "stupid analyzer" sees issues than the code is very likely in a very bad shape.
Adding such tools later on in the development is like activating warnings post factum: You'll get drowned in issues.
Especially in such critical domains as file-systems I would actually expect that the developers are using "the best tools money can buy" (or at least the best OpenSource tools available).
"Still fixing bugs found by some code analyzer" doesn't sound like someone should have much trust with their data in something like ZFS, to be honest… The statement sounds actually quite scary to me.
- NSA Cybersecurity Information Sheet remarks on C and C++.
-
IKOS: Static analyzer for C/C++ based on the theory of Abstract Interpretation
They have very unusual license which I have never seen before: https://github.com/NASA-SW-VnV/ikos/blob/master/LICENSE.txt
Is anyone familiar with it? Is it OSI certified? (it's not on the OSI's site).
- Is there a project like MIRI but for C++
-
(x-post) Why static analysis on C projects is not widespread already?
Yeah there are tools that require adding contracts as comments. But again, there are also friction-less tools that don't require any changes (for example a NASA one).
checkedc
- The NSA list of memory-safe programming languages has been updated
-
The Fil-C Manifesto: Garbage In, Memory Safety Out
https://github.com/microsoft/checkedc
Also, one can combine subsets of C with FOSS, static analyzers that can handle those subsets. Then, compose only in ways that the tools can handle. Then, combinatorial and fuzz testing of the interface composition.
I know you’re doing the project for fun while exploring specific ways to achieve your goals. So, these are just some links and concepts that might help on your journey. Lots of folks don’t know about prior work in this area. So, I keep passing it on.
-
My Bad Habit of Hoarding Information
- [Checked C](https://github.com/microsoft/checkedc) - extensions to make C safer #cpp
- Checked C
- Is it possible to have a superset of the C programming languages standard that is as safe as Rust?
- Checked C by Microsoft Research
-
Azure CTO: “It's time to halt starting any new projects in C/C++ ”
Yes. Microsoft Research is working on "Checked C": https://www.microsoft.com/en-us/research/project/checked-c/
As a test, someone ported FreeBSD's networking stack to Checked C. It was easy and there was no overhead to performance and binary size.
-
I want to learn csharp man
Haha. I think they did ultimately agree. Thus a later research project is: Checked-C
What are some alternatives?
Triton - Triton is a dynamic binary analysis library. Build your own program analysis tools, automate your reverse engineering, perform software verification or just emulate code.
koka - Koka language compiler and interpreter
ardupilot - ArduPlane, ArduCopter, ArduRover, ArduSub source
rust.ko - A minimal Linux kernel module written in rust.
IntegerAbsoluteDifferenceCpp - Computing the difference between two integer values in C++. Turns out this isn't trivial.
manyclangs - Repository hosting unofficial binary pack files for many commits of LLVM
cppbestpractices - Collaborative Collection of C++ Best Practices. This online resource is part of Jason Turner's collection of C++ Best Practices resources. See README.md for more information.
c2rust - Migrate C code to Rust
codechecker - CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy
linux - Linux kernel source tree
z3 - The Z3 Theorem Prover
dafny - Dafny is a verification-aware programming language