Buidling @TarantoolDB. I make software suck less: software quality, testing, and verification. Writing to @openbsdnow and https://teapawt.net/t.co/ccSm1xODGX.
Joined December 2007
- Tweets6.7K
- Following451
- Followers581
- Likes843
Sergey Bronnikov retweeted
Just got the first actual PyPy JIT optimizer bug that Z3 found! And it spits out a nice example of values that show the miscompilation.
The bug is again about integer overflow, but this time it is in the common subexpression elimination (CSE) logic.
Sergey Bronnikov retweeted
I'm trying to reflect on bugs that I find, particularly those that I introduced myself. Will add them to this thread:
Sergey Bronnikov retweeted
Now blog post by @cfbolz:
'Finding Simple Rewrite Rules for the JIT with Z3'
How to use the Z3 API to find simple rewrites of integer operations, such as x & 0 -> 0
pypy.org/posts/2024/07/findi…
Sergey Bronnikov retweeted
Sharing slides and video for my keynote at OSS EU'24: "Securing the software commons: Standards, Automation, and AI for a Resilient Open Source Future"
Slides: drive.google.com/file/d/186i…
Video: youtube.com/watch?v=NwI2MkAN…
Sergey Bronnikov retweeted
I'm happy to announce the release of a new open-source library we've been working on: Go library for structure-aware fuzzing, designed as an analogue to libprotobuf-mutator. Fuzz your gRPC APIs and integrate into SSDLC.
github.com/yandex-cloud/go-p…
#fuzzing #go #grpc #ssdlc
Sergey Bronnikov retweeted
I’ve posted a mid-year update for my GCC translation validation tool, smtgcc, to the GCC mailing list:
gcc.gnu.org/pipermail/gcc/20…
Sergey Bronnikov retweeted
There's been a recent addition to the list, thanks to @estet. A bug in a preliminary version of a Software Transactional Memory (STM) algorithm.
ALT Citation of Alexey Belyaev - "Verifying an algorithm for transaction memory support", published in 2010 in Russian.
Sergey Bronnikov retweeted
"Model Checking Futexes", to be presented at SPIN, part of @ETAPSconf, in April. Joint with Hugues Evrard.
Shows how model checking can be used to understand the mind-blowing (for me!) subtleties of futex-based synchronisation primitives.
doc.ic.ac.uk/~afd/homepages/…
Sergey Bronnikov retweeted
Excited to present new(?) approach to #fuzzing where one doesn't need to write fuzz functions.
Wanna fuzz all binaries on github - no problem.
Just give the fuzzer binaries to test. No false positives & 100% fidelity.
Blender: whole-program fuzzing:
github.com/dvyukov/centipede…
Sergey Bronnikov retweeted
My blog post about #fuzzing #go project golang/image: github.com/ispras/oss-sydr-f…
0. Changing existing fuzz target to find new bugs.
1. Approach for code coverage collection after fuzzing with go-fuzz libFuzzer.
2. Go panic triage with #casr.
3. Fix: github.com/golang/image/pull…
Sergey Bronnikov retweeted
This tweet is for FUZZING enthusiasts !! Our research group at NUS (abhikrc.com/projects/Fuzz/) is looking for practitioners and researchers to take this survey about software testing: lnkd.in/g6f_2ftd
We'll donate $5 USD to Doctors Without Borders (up to 100 responses)!
Sergey Bronnikov retweeted
luzer: A coverage-guided, native Lua fuzzing engine
by @estet
lobste.rs/s/pc8zx8 #lua #programming #security #testing
github.com/ligurio/luzer
Sergey Bronnikov retweeted
Fuzzilli (github.com/googleprojectzero…), the great coverage-guided fuzzer for dynamic language interpreters based on a custom intermediate language built by @5aelo, is finally documented in a paper. You can find the paper at ndss-symposium.org/ndss-pape…
Fascinating discussion ongoing in Fuzzing session at #NDSS23: FUZZILLI: Fuzzing for JavaScript JIT Compiler Vulnerabilities.
Sergey Bronnikov retweeted
We’re seeking an OCaml software engineer to develop the software ecosystem and smart contract language of an open-source blockchain platform.
Learn more: serokell.io/jobs/ocaml-new
Sergey Bronnikov retweeted
And not to anyone’s surprise, fuzzing multithreaded programs by inserting yield() and other primitives also is more than 20 years old: cs.purdue.edu/homes/xyzhang/… It wasn’t called “fuzzing” at the time, but just “test generation”, but it would be great to recognize history – at Saarbrücken, Germany
Sergey Bronnikov retweeted
6 yrs since @Google OSS-Fuzz started, reached 850 projects, fixed 8,800 vulns & 28,000 stability bugs & next we are bumping up OSS-Fuzz rewards: more reward categories for improving coverage and horizontal leet rewards for impacting hundreds of projects - security.googleblog.com/2023…
Sergey Bronnikov retweeted
Quote of the day: "Static analysis has found a few bugs in SQLite, but those are the exceptions. More bugs have been introduced into SQLite while trying to get it to compile without warnings than have been found by static analysis."
Source: sqlite.org/testing.html
Sergey Bronnikov retweeted
Looking for ideas for new fuzz targets for your project? Check out the updated documentation for Fuzz Introspector showing how it can help fuzz-introspector.readthedoc…
