Alongside the Bytecode Alliance, Fastly’s WebAssembly team recently led a rigorous security assessment of Cranelift, an open-source, next-generation code generator for use in WebAssembly to provide sandbox security functionality.

Building protocols in a way that anticipates future change in order to prevent ossification is critical. Because it’s impossible to upgrade everyone on the internet at the same time; it needs to be possible to introduce changes gradually, without harming communication where only one party understands the change — and this is everyone’s responsibility.

QUIC version 1 is officially formalized, and QUIC deployments will now move away from using temporary draft versions to the newly minted version 1.

As part of May’s Asian American and Pacific Islander (AAPI) Heritage Month, we hosted a panel of Asian leaders from tech organizations that reflected on ways their cultural backgrounds impacted their career journeys and ascent into leadership roles.

Authentication is one of the most obvious uses for edge computing. Understanding who your users are as early and as close as possible to their location yields powerful customizations and speedy responses. But there's more than one way to think about how to apply an authentication scheme at the edge.

As Kubernetes has become widespread for container orchestration needs, it’s natural for security questions to arise. Here are answers to the Kubernetes questions we hear most often.

The bug identified in the Cranelift x64 backend performs a sign-extend instead of a zero-extend on a value loaded from the stack, when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, the x64 compiler relies on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.

We recently discovered a compiler bug in part of the WebAssembly compiler that we use for Compute@Edge, that could have allowed a WebAssembly module to access memory outside of its sandboxed heap. But because of the people, processes, and tools we have in place, the bug was caught and patched on our infrastructure before it was exploited.

The bug identified in the Cranelift x64 backend performs a sign-extend instead of a zero-extend on a value loaded from the stack, when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, the x64 compiler relies on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.

Online payments giant PayPal uses Fastly’s edge platform to deliver a more secure, faster, and more reliable user experience at a time when digital payments are surging.

Following the DRY principle isn’t just for engineers. It also cuts the time it takes to make updates in multiple places and reduces errors for our documentation team.

Over the past few months, we’ve rolled out a series of design improvements focused on text readability, easing eye-strain, and providing a seamless brand experience.

Zig is a general purpose programming language, meaning that if you have in front of you something that looks like a Von Neumann-ish, Turing-complete machine, you should be able to comfortably program it with Zig. Lately there has been a lot of interest in two such (virtual) machines: BPF and WebAssembly.

GitHub Actions for Compute allow you to transition from a manually deployed application to a fully automated deployment workflow with ease and wrap the Fastly CLI to provide an easy way to keep your application up to date.

It's always been possible to create content programmatically, and with the advent of our serverless compute environment, we've made it possible to create and transform content more efficiently and powerfully than ever before.

Throwing new security tools at new threats results in scattershot protection and builds technical debt. Organizations need uniform protection for applications and APIs, regardless of where they live.

New Fastly next-gen WAF dashboards surface security telemetry from more than 20 new signals for advanced attack scenarios, such as account takeover, credit card validation, and password reset.

Fastly now offers logging support for Amazon Kinesis Data Streams, as well as AWS Identity and Access Management (IAM) functionality for S3 and Kinesis logging endpoints.