QuantaStor
QuantaStor, a unified Software Defined Storage platform, is designed to scale up and down to simplify storage management and reduce overall storage costs. QuantaStor storage grids can be configured to support complex workflows that span datacenters and sites. QuantaStor's storage technology includes a built-in Federated Management System that allows QuantaStor servers and clients to be combined to make management and automation easier via CLI and RESTAPIs. QuantaStor's layered architecture gives solution engineers unprecedented flexibility and allows them to design applications that maximize workload performance and fault tolerance for a wide variety of storage workloads. QuantaStor provides end-to-end security coverage that allows multi-layer data protection for cloud and enterprise storage deployments.
Learn more
Ditto
Ditto is the only mobile database with built-in edge device connectivity and resiliency, enabling apps to synchronize without relying on a central server or constant cloud connectivity. With billions of edge devices and deskless workers driving operations and revenue, businesses are hitting the limits of what traditional cloud architectures can offer. Trusted by Chick-fil-A, Delta, Lufthansa, Japan Airlines, and more, Ditto is pioneering the edge-native revolution, transforming how businesses connect, sync, and operate at the edge. By eliminating hardware dependencies, Ditto’s software-driven networking is enabling businesses to build faster, more resilient systems that thrive at the edge – no Wi-Fi, servers, or cloud required.
Through the use of CRDTs and P2P mesh replication, Ditto's technology enables you to build collaborative, resilient applications where data is always available and up-to-date for every user, and can even be synced in completely offline situations. This allows you to keep mission-critical systems online when it matters most.
Ditto uses an edge-native architecture. Edge-native solutions are built specifically to thrive on mobile and edge devices, without relying solely on cloud-based services. Devices running Ditto apps can discover and communicate with each other directly, forming an ad-hoc mesh network rather than routing everything through a cloud server. The platform automatically handles the complexity of discovery and connectivity using both online and offline channels – Bluetooth, peer-to-peer Wi-Fi, local LAN, WiFi, Cellular – to find nearby devices and sync data changes in real-time.
Learn more
LibFuzzer
LibFuzzer serves as an in-process, coverage-guided engine for evolutionary fuzzing. By being linked directly with the library under examination, it injects fuzzed inputs through a designated entry point, or target function, allowing it to monitor the code paths that are executed while creating variations of the input data to enhance code coverage. The coverage data is obtained through LLVM’s SanitizerCoverage instrumentation, ensuring that users have detailed insights into the testing process. Notably, LibFuzzer continues to receive support, with critical bugs addressed as they arise. To begin utilizing LibFuzzer with a library, one must first create a fuzz target—this function receives a byte array and interacts with the API being tested in a meaningful way. Importantly, this fuzz target operates independently of LibFuzzer, which facilitates its use alongside other fuzzing tools such as AFL or Radamsa, thereby providing versatility in testing strategies. Furthermore, the ability to leverage multiple fuzzing engines can lead to more robust testing outcomes and clearer insights into the library's vulnerabilities.
Learn more
syzkaller
Syzkaller functions as an unsupervised, coverage-guided fuzzer aimed at exploring vulnerabilities within kernel environments, offering support for various operating systems such as FreeBSD, Fuchsia, gVisor, Linux, NetBSD, OpenBSD, and Windows. Originally designed with a focus on fuzzing the Linux kernel, its capabilities have been expanded to encompass additional operating systems over time. When a kernel crash is identified within one of the virtual machines, syzkaller promptly initiates the reproduction of that crash. By default, it operates using four virtual machines for this reproduction process and subsequently works to minimize the program responsible for the crash. This reproduction phase can temporarily halt fuzzing activities, as all VMs may be occupied with reproducing the identified issues. The duration for reproducing a single crash can vary significantly, ranging from mere minutes to potentially an hour, depending on the complexity and reproducibility of the crash event. This ability to minimize and analyze crashes enhances the overall effectiveness of the fuzzing process, allowing for better identification of vulnerabilities in the kernel.
Learn more