Microsoft Ransomware, Apple in trouble, and WebAssembly in OCI containers
-
How Ransomware Is Causing Chaos in American Schools [iophk: Windows TCO]
Sierra College was just one of 1,043 schools and colleges—part of 62 school districts and the campuses of 26 colleges and universities—hit by ransomware hackers in 2021, according to Emsisoft, a cybersecurity company that tracks ransomware incidents. The company reports that, so far in 2022, there have been 27 districts with 1,735 schools hit with ransomware.
-
EU Passes Law to Switch iPhone to USB-C by End of 2024
The proposal, known as a directive, forces all consumer electronics manufacturers who sell their products in Europe to ensure that a wide range of devices feature a USB-C port. This "common port" will be a world-first statute and impact Apple in particular since it widely uses the Lightning connector instead of USB-C on many of its devices. MEPs claim that the move will reduce electronic waste, address product sustainability, and make use of different devices more convenient.
The directive received 602 votes in favor, 13 votes against, and eight abstentions. A press release issued by the European Parliament earlier today states: [...]
-
Long-awaited common charger for mobile devices will be a reality in 2024
Regardless of their manufacturer, all new mobile phones, tablets, digital cameras, headphones and headsets, handheld videogame consoles and portable speakers, e-readers, keyboards, mice, portable navigation systems, earbuds and laptops that are rechargeable via a wired cable, operating with a power delivery of up to 100 Watts, will have to be equipped with a USB Type-C port.
All devices that support fast charging will now have the same charging speed, allowing users to charge their devices at the same speed with any compatible charger.
-
Use OCI containers to run WebAssembly workloads
WebAssembly (also referred to as Wasm) has gained popularity as a portable binary instruction format with an embeddable and isolated execution environment for client and server applications. Think of WebAssembly as a small, fast, efficient, and very secure stack-based virtual machine designed to execute portable bytecode that doesn't care what CPU or operating system it runs on. WebAssembly was initially designed for web browsers to be a lightweight, fast, safe, and polyglot container for functions, but it's no longer limited to the web.
On the web, WebAssembly uses the existing APIs provided by browsers. WebAssembly System Interface (WASI) was created to fill the void between WebAssembly and systems running outside the browser. This enables non-browser systems to leverage the portability of WebAssembly, making WASI a good choice for portability while distributing and isolation while running the workload.
WebAssembly offers several advantages. Because it is platform neutral, one single binary can be compiled and executed on a variety of operating systems and architectures simultaneously, with a very low disk footprint and startup time. Useful security features include module signing and security knobs controllable at the run-time level rather than depending on the host operating system's user privilege. Sandboxed memory can still be managed by existing container tools infrastructure.
In this article, I will walk through a scenario for configuring container runtimes to run Wasm workloads from lightweight container images.