惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
V
V2EX
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Jina AI
Jina AI
小众软件
小众软件
量子位
博客园 - 三生石上(FineUI控件)
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - Franky
博客园_首页
IT之家
IT之家
S
SegmentFault 最新的问题
博客园 - 叶小钗
阮一峰的网络日志
阮一峰的网络日志
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 聂微东
T
Tailwind CSS Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
爱范儿
爱范儿
月光博客
月光博客
有赞技术团队
有赞技术团队
H
Help Net Security
云风的 BLOG
云风的 BLOG

Open Container Initiative

OCI Runtime Spec v1.3 - Open Container Initiative OCI Image and Distribution Specs v1.1 Releases OCI Runtime Spec v1.2 - Open Container Initiative OCI in 2024 and TOB Election Results Summary of Upcoming Changes in OCI Image and Distribution Specs v1.1 OCI at The Container Plumbing Conference OCI in 2023 and TOB Election Results OCI in 2022 and TOB Election Results OCI Member Spotlight – Chainguard Calling All Registries to Submit OCI Conformance! OCI Summit 2021 - Open Container Initiative OCI in 2021 and TOB Election Results Consuming Public Content - Open Container Initiative OCI accepts new project, umoci Introducing and open sourcing the OCI Icon Set Open Sourcing runc Security Audit Container Journal – “OCI Launches Artifacts Project to Reduce Registries Required” New OCI Artifacts Project - Open Container Initiative Open Container Initiative Explained…with Dolls! OCI 2019 Elections and New TOB Lineup 2018’s Biggest Moments + What’s Coming for OCI in 2019 Bringing OCI images to the desktop with Flatpak OCI Image Support Comes to Open Source Docker Registry Open Container Initiative Welcomes Alibaba Cloud as Newest Member PouchContainer – How OCI Specifications Power Alibaba CRI-O – How Standards Power a Container Runtime OCI Member Spotlight – OpenStack (Kata Containers) Teaming up with Docker to Support a Diverse Container Ecosystem The New Stack – “Open Container Initiative Creates a Distribution Specification for Registries” SDxCentral – “OCI Standardizes Container Image Distribution Based on Docker Registry”
Introducing fuzzing for runC and Umoci
map[name:Open Container Initiative tag:oci] · 2021-05-06 · via Open Container Initiative

Through March and April 2021 Ada Logics contributed an extensive fuzzing infrastructure for the two Opencontainers projects runC and Umoci. The reason for initiating fuzz testing in the first place is to stress test projects for bugs and vulnerabilities. Fuzzing does this by generating pseudo-random inputs and leveraging coverage-based genetic algorithms to identify important inputs that may impose bugs in software. The technique has been used for more than two decades and in recent years has had a lot of momentum, including being applied on Golang programs (which is the language of runC and Umoci). Fuzzing can help with both finding bugs that have been present in code for a long time as well as finding recently-introduced bugs before they ship to production. In this project most of the fuzzers were set up to run in a continuous manner which makes them particularly well-suited for catching bugs early in the development cycle.

In total 17 fuzz tests were contributed to Umoci and runC, and they were submitted to both projects’ Github repositories. The fuzzers were implemented by way of the state-of-the-art go-fuzz engine which has been used by developers and researchers for many years to find a multitude of different types of bugs in open source Golang projects.

Ada Logics integrated runC into OSS-fuzz which is a service where critical open source projects can run their fuzzers continuously using computational power provided by Google. To date, OSS-Fuzz has helped find more than 25,000 bugs in software, including critical bugs in Golang itself that could take down the Ethereum network. As Umoci does not qualify for OSS-fuzz integration, Ada Logics provided an environment to make it easy for maintainers and contributors to run the fuzzers locally.

The fuzzers did not find any bugs during the development phase itself which is a testament to the robustness of the two projects. However, many of the fuzzers still have a lot of code within their reach that is unexplored and OSS-Fuzz will continue to run the fuzzers leaving room for finding bugs and vulnerabilities.

The full report of the engagement can be found here.