Mozilla: Librsvg, Bytecode Alliance, and Extensions in Firefox 71

-
CSS in librsvg is now in Rust, courtesy of Mozilla Servo
Summary: after an epic amount of refactoring, librsvg now does all CSS parsing and matching in Rust, without using libcroco. In addition, the CSS engine comes from Mozilla Servo, so it should be able to handle much more complex CSS than librsvg ever could before.
-
Librsvg Continues Rust Conquest, Pulls In CSS Parsing Code From Mozilla Servo
For about three years now GNOME's SVG rendering library has been transitioning to Rust. This library, librsvg, now makes further use of Rust around its CSS parsing code and Mozilla's Servo is doing some of that heavy lifting.
Librsvg is employing the CSS engine from Mozilla's Servo engine in order to be written in Rust while also having the benefit of being able to handle more complex CSS code than the previous implementation.
-
Announcing the Bytecode Alliance: Building a secure by default, composable future for WebAssembly
Today we announce the formation of the Bytecode Alliance, a new industry partnership coming together to forge WebAssembly’s outside-the-browser future by collaborating on implementing standards and proposing new ones. Our founding members are Mozilla, Fastly, Intel, and Red Hat, and we’re looking forward to welcoming many more.
-
New Bytecode Alliance Brings the Security, Ubiquity, and Interoperability of the Web to the World of Pervasive Computing
The Bytecode Alliance is a newly-formed open source community dedicated to creating new software foundations, building on standards such as WebAssembly and WebAssembly System Interface (WASI). Mozilla, Fastly, Intel, and Red Hat are founding members.
The Bytecode Alliance will, through the joint efforts of its contributing members, deliver a state-of-the-art runtime environment and associated language toolchains, where security, efficiency, and modularity can all coexist across the widest possible range of devices and architectures. Technologies contributed and collaboratively evolved through the Alliance leverage established innovation in compilers, runtimes, and tooling, and focus on fine-grained sandboxing, capabilities-based security, modularity, and standards such as WebAssembly and WASI.
-
Mozilla + Intel + Red Hat Form The Bytecode Alliance To Run WebAssembly Everywhere
Mozilla, Fastly, Intel, and Red Hat have announced the Bytecode Alliance as a new initiative built around WebAssembly and focused on providing a secure-by-default bytecode that can run from web browsers to desktops to IoT/embedded platforms.
"Together, we’re putting in solid, secure foundations that can make it safe to use untrusted code, no matter where you’re running it—whether on the cloud, natively on someone’s desktop, or even on a tiny IoT device," announced Mozilla.
-
Extensions in Firefox 71
Firefox 71 is a light release in terms of extension changes. I’d like to tell you about a few interesting improvements nevertheless.
Thanks to Nils Maier, there have been various improvements to the downloads API, specifically in handling download failures. In addition to previously reported failures, the browser.downloads.download API will now report an error in case of various 4xx error codes. Similarly, HTTP 204 (No Content) and HTTP 205 (Reset Content) are now treated as bad content errors. This makes the API more compatible with Chrome and gives developers a way to handle these errors in their code. With the new allowHttpErrors parameter, extensions may also ignore some http errors when downloading. This will allow them to download the contents of server error pages.
-
- Login or register to post comments
Printer-friendly version
- 5224 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
Android Document Scanning and Developer-Focused TV Box
| Improving the security model of the LVFS
There are lots of layers of security in the LVFS and fwupd design, including restricted account modes, 2FA, and server side AppStream namespaces. The most powerful one is the so-called vendor-id that the vendors cannot assign themselves, and is assigned by me when creating the vendor account on the LVFS. The way this works is that all firmware from the vendor is tagged with a vendor-id string like USB:0x056A which in this case matches the USB consortium vendor assigned ID. Client side, the vendor-id from the signed metadata is checked against the physical device and the firmware is updated only if the ID matches. This ensures that malicious or careless users on the LVFS can never ship firmware updates for other vendors hardware. About 90% of the vendors on the LVFS are locked down with this mechanism.
Some vendors have to have IDs that they don’t actually own, a good example here is for a DFU device like the 8bitdo controllers. In runtime mode they use the USB-assigned 8bitdo VID, but in bootloader mode they use a generic VID which is assigned to the chip supplier as they are using the reference bootloader. This is obviously fine, and both vendor IDs are assigned to 8bitdo on the LVFS for this reason. Another example is where Lenovo is responsible for updating Lenovo-specific NVMe firmware, but where the NVMe vendor isn’t always Lenovo’s PCI ID.
|
Programming: Vim, Qt Shader and Python
| Games: Pygame, The Long Dark, DXVK and Shovel Knight
|
Mozilla partners with Intel, Red Hat and Fastly
Mozilla partners with Intel, Red Hat and Fastly to take WebAssembly beyond the browser
Another privacy publicity stunt
Mozilla plays role in Kenya’s adoption of crucial data protection law
Tracking Diaries with Tiffany LaTrice Williams
Tracking Diaries with Tiffany LaTrice Williams
LWN and Original About Bytecode Alliance
Announcing the Bytecode Alliance
Announcing the Bytecode Alliance: Building a secure by default, composable future for WebAssembly
Slashdot and Neowin
Mozilla, Intel, and More Form the Bytecode Alliance To Take WebAssembly Beyond Browsers
Mozilla, Intel, and more form the Bytecode Alliance to take WebAssembly beyond browsers
Four go wild for wasm: Corporate quartet come together
Four go wild for wasm: Corporate quartet come together to build safe WebAssembly sandbox
The ByteCode Alliance wants to bring binary apps...
The ByteCode Alliance wants to bring binary apps into your browser
More on Bytecode Alliance
Mozilla, Intel and Red Hat form Bytecode Alliance for better open-source security
Using WebAssembly from .NET with Wasmtime
Using WebAssembly from .NET with Wasmtime