oss-fuzz
imaginary
Our great sponsors
oss-fuzz | imaginary | |
---|---|---|
31 | 6 | |
9,850 | 5,323 | |
3.8% | - | |
9.9 | 4.5 | |
6 days ago | 2 months ago | |
Shell | Go | |
Apache License 2.0 | MIT License |
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.
oss-fuzz
- Xz: Disable ifunc to fix Issue 60259
-
Backdoor in upstream xz/liblzma leading to SSH server compromise
> because the ifunc code was breaking with all sorts of build options and obviously caused many problems with various sanitizers
for example, https://github.com/google/oss-fuzz/pull/10667
-
Ask HN: Any Good Fuzzer for gRPC?
Have you tried Googles grpc fuzzer?
https://github.com/google/oss-fuzz/blob/master/projects/grpc...
-
Pacemaker should be running open source software
https://www.fda.gov/medical-devices/digital-health-center-ex...
oss-fuzz: https://github.com/google/oss-fuzz :
> We support the libFuzzer, AFL++, and Honggfuzz fuzzing engines in combination with Sanitizers, as well as ClusterFuzz, a distributed fuzzer execution environment and reporting tool.
> Currently, OSS-Fuzz supports C/C++, Rust, Go, Python, Java/JVM, and JavaScript code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.
-
Fuzz Testing Is the Best Thing to Happen to Our Application Tests
I love fuzzing as a technique and use it quite regularly, but running AFL++ on even a single program occupies all threads of a high end AMD server for weeks. I'm running it locally so only paying for the electricity. If it was a cloud instance it would cost a small fortune. I think this is a reason it is not used more widely.
I will note that Google have a programme for doing fuzz testing on open source projects using computer from their cloud: https://google.github.io/oss-fuzz/
- Fixed Spelling Errors or Typos
- ELI5: How can downloading a pdf or word file give you a virus?
- OSS-Fuzz β continuous fuzzing for open source software
-
Mosh: An Interactive Remote Shell for Mobile Clients (2012) [pdf]
Yes, mosh has fuzz tests in oss-fuzz [1].
[1] https://github.com/google/oss-fuzz/tree/master/projects/mosh
-
Java Fuzzing with Jazzer compared to Symflower
We will explore how Jazzer is used to automatically generate malicious inputs for Java programs, and how it compares to Symflower, which can automatically generate unit tests to uncover bugs and errors in your code. With the help of Jazzer, many bugs - some of them even in the OpenJDK - were found already. Also, as of March 2021, Jazzer is officially part of OSS-Fuzz, Google's cloud fuzzing engine. It should be noted that Jazzer is a pure "bug detection" utility that finds reproducers for errors in user code. Symflower can do the same, but provides additional functionalities to boost developer productivity, like generating high coverage unit tests and providing test templates for the software developer or tester.
imaginary
- Golang libraries for image compression / resizing / manipulation
-
Plugin to auto-convert uploaded images to WEBP?
WebP also frequently produces lower quality or blurry images: - https://wordpress.org/support/topic/images-going-blurry/ - https://github.com/h2non/imaginary/issues/240
-
Announcing Nextcloud Hub 3 β Brand New Design and Photos 2.0 with Editor and AI
One thing I didn't mention that AIO includes is a container called imaginary which is written in Go and processes images. I think this is mainly used here for generating image previews in NC.
-
Imagor 0.8.5: fast image processing server - now with animated GIF resize, crop, watermark and more
Thanks. This is new to me. How is it different from https://github.com/h2non/imaginary?
-
Imagor is a fast, Docker-ready image processing server written in Go
There is also battle-tested imaginary tool [1], offering similar functionality and much more, also using libvips
-
Deploy your own image processing API using Imaginary
Imaginary is a fast HTTP microservice written in Go allowing high-level image processing. Behind the scene, imaginary uses bimg and libvips libraries to perform the image manipulations.
What are some alternatives?
AFLplusplus - The fuzzer afl++ is afl with community patches, qemu 5.1 upgrade, collision-free coverage, enhanced laf-intel & redqueen, AFLfast++ power schedules, MOpt mutators, unicorn_mode, and a lot more!
imagick - Go binding to ImageMagick's MagickWand C API
fuzzilli - A JavaScript Engine Fuzzer
resize - Pure golang image resizing
ffmpeg-libav-tutorial - FFmpeg libav tutorial - learn how media works from basic to transmuxing, transcoding and more. Translations: πΊπΈ π¨π³ π°π· πͺπΈ π»π³ π§π·
imaging - Imaging is a simple image processing package for Go
libfuzzer - Thin interface for libFuzzer, an in-process, coverage-guided, evolutionary fuzzing engine.
bimg - Go package for fast high-level image processing powered by libvips C library
uafuzz - UAFuzz: Binary-level Directed Fuzzing for Use-After-Free Vulnerabilities
Primitive Pictures - Reproducing images with geometric primitives.
ffmpeg-tutorial - A set of tutorials that demonstrates how to write a video player based on FFmpeg
thumbor - The quickest way to run thumbor.