Grain Stuck In Ukraine: The Fragmented Nature Of Modern-Day Railways

June 23, 2022 by Maya Posch 79 Comments

The war in Ukraine has upset the global food market, and the surprising reason is not that Ukrainian wheat isn’t being harvested, but rather that it can’t leave the country. With Russia blockading sea ports, the only way out for Ukrainian grain is by train. And this exposes the long-hidden patchwork of railway tracks and train standards: trains can’t simply cross the border from Ukraine to Poland on their way to a sea port because the tracks don’t match.

Even beyond the obvious issues of connecting differently sized physical railway tracks — the track gauge — there are different signaling systems, different voltages for electrical trains, different loading and structural gauges, and so on. In Europe today, the political history of the past few hundred years can still be traced back using its railroads, with some parts of the European Union still on 1,520 mm Soviet-standard gauge, rather than the 1,435 mm Standard Gauge, which is also known as Stephenson Gauge, European Gauge, etc.

These complications explain why for example with the current war in Ukraine its railways into the rest of Europe aren’t used more for transporting grain and other cargo: with Ukraine using 1,520 mm gauge, all cargo has to be transferred to different trains at the Ukraine-EU border or have bogies swapped. Although some variable gauge systems exist, these come with their own set of limitations.

In light of this it’s not hard to see why standardizing on a single international or even European track gauge is complicated due to having to replace or adapt all tracks and rolling stock, even before considering the aforementioned voltage and signaling differences. All which may lead one to wonder whether we’ll ever see a solution to this historically grown problem.

Continue reading “Grain Stuck In Ukraine: The Fragmented Nature Of Modern-Day Railways” →

NASA Mission Off To Rough Start After Astra Failure

June 17, 2022 by Tom Nardi 14 Comments

When Astra’s diminutive Rocket 3.3 lifted off from its pad at the Cape Canaveral Space Force Station on June 12th, everything seemed to be going well. In fact, the mission was progressing exactly to plan right up until the end — the booster’s second stage Aether engine appeared to be operating normally until it abruptly shut down roughly a minute ahead of schedule. Unfortunately, orbital mechanics are nothing if not exacting, and an engine burn that ends a minute early might as well never have happened at all.

According to the telemetry values shown on-screen during the live coverage of the launch, the booster’s upper stage topped out at a velocity of 6.573 kilometers per second, well short of the 7.8 km/s required to attain a stable low Earth orbit. While the video feed was cut as soon as it was clear something had gone wrong, the rigid physics of spaceflight means there’s little question about the sequence of events that followed. Without the necessary energy to stay in orbit, the upper stage of the rocket would have been left in a sub-orbital trajectory, eventually reentering the atmosphere and burning up a few thousand kilometers downrange from where it started.

An unusual white plume is seen from the engine as it shuts down abruptly.

Of course, it’s no secret that spaceflight is difficult. Doubly so for startup that only has a few successful flights under their belt. There’s no doubt that Astra will determine why their engine shutdown early and make whatever changes are necessary to ensure it doesn’t happen again, and if their history is any indication, they’re likely to be flying again in short order. Designed for a Defense Advanced Research Projects Agency (DARPA) competition that sought to spur the development of cheap and small rockets capable of launching payloads on short notice, Astra’s family of rockets have already demonstrated unusually high operational agility.

Astra, and the Rocket 3.3 design, will live to fly again. But what of the payload the booster was due to put into orbit? That’s a bit more complicated. This was the first of three flights that were planned to assemble a constellation of small CubeSats as part of NASA’s TROPICS mission. The space agency has already released a statement saying the mission can still achieve its scientific goals, albeit with reduced coverage, assuming the remaining satellites safely reach orbit. But should one of the next launches fail, both of which are currently scheduled to fly on Astra’s rockets, it seems unlikely the TROPICS program will be able to achieve its primary goal.

So what exactly is TROPICS, and why has NASA pinned its success on the ability for a small and relatively immature launch vehicle to make multiple flights with their hardware onboard? Let’s take a look.

Continue reading “NASA Mission Off To Rough Start After Astra Failure” →

NASA Turns To Commercial Partners For Spacesuits

June 3, 2022 by Tom Nardi 27 Comments

When NASA astronauts aboard the International Space Station have to clamber around on the outside of the orbiting facility for maintenance or repairs, they don a spacesuit known as the Extravehicular Mobility Unit (EMU). Essentially a small self-contained spacecraft in its own right, the bulky garment was introduced in 1981 to allow Space Shuttle crews to exit the Orbiter and work in the craft’s cavernous cargo bay. While the suits did get a minor upgrade in the late 90s, they remain largely the product of 1970s technology.

Not only are the existing EMUs outdated, but they were only designed to be use in space — not on the surface. With NASA’s eyes on the Moon, and eventually Mars, it was no secret that the agency would need to outfit their astronauts with upgraded and modernized suits before moving beyond the ISS. As such, development of what would eventually be the Exploration Extravehicular Mobility Unit (xEMU) dates back to at least 2005 when it was part of the ultimately canceled Constellation program.

NASA’s own xEMU suit won’t be ready by 2025.

Unfortunately, after more than a decade of development and reportedly $420 million in development costs, the xEMU still isn’t ready. With a crewed landing on the Moon still tentatively scheduled for 2025, NASA has decided to let their commercial partners take a swing at the problem, and has recently awarded contracts to two companies for a spacesuit that can both work on the Moon and replace the aging EMU for orbital use on the ISS.

As part of the Exploration Extravehicular Activity Services (xEVAS) contract, both companies will be given the data collected during the development of the xEMU, though they are expected to create new designs rather than a copy of what NASA’s already been working on. Inspired by the success of the Commercial Crew program that gave birth to SpaceX’s Crew Dragon, the contract also stipulates that the companies will retain complete ownership and control over the spacesuits developed during the program. In fact, NASA is even encouraging the companies to seek out additional commercial customers for the finished suits in hopes a competitive market will help drive down costs.

There’s no denying that NASA’s partnerships with commercial providers has paid off for cargo and crew, so it stands to reason that they’d go back to the well for their next-generation spacesuit needs. There’s also plenty of incentive for the companies to deliver a viable product, as the contact has a potential maximum value of $3.5 billion. But with 2025 quickly approaching, and the contact requiring a orbital shakedown test before the suits are sent to the Moon, the big question is whether or not there’s still enough time for either company to make it across the finish line.

Continue reading “NASA Turns To Commercial Partners For Spacesuits” →

The Great Euro Sat Hack Should Be A Warning To Us All

June 2, 2022 by Lewin Day 46 Comments

Military officials and civilian security researchers have been warning us for years: cyberattacks are becoming a very real part of modern warfare. Far from being limited to military targets, cyberattacks can take out everything from vital public infrastructure to commercial and industrial operations, too.

In the early hours of February 24, as the Russian invasion force began raining missiles on Ukrainian cities, another attack was in progress in the digital realm. Suddenly, satellite terminals across Europe were going offline, with many suffering permanent damage from the attack.

Details remain hazy, but researchers and military analysts have pieced together a picture of what happened that night. The Great Euro Sat Hack prove to be the latest example of how vulnerable our digital infrastructure can be in wartime.

Continue reading “The Great Euro Sat Hack Should Be A Warning To Us All” →

Knowing Your Place: The Implications Of GPS Spoofing And Jamming

May 23, 2022 by Maya Posch 30 Comments

Artificial satellites have transformed the world in many ways, not only in terms of relaying communication and for observing the planet in ways previously inconceivable, but also to enable incredibly accurate navigation. A so-called global navigation satellite system (GNSS), or satnav for short, uses the data provided by satellites to pin-point a position on the surface to within a few centimeters.

The US Global Positioning System (GPS) was the first GNSS, with satellites launched in 1978, albeit only available to civilians in a degraded accuracy mode. When full accuracy GPS was released to the public under the 1990s Clinton administration, it caused a surge in the uptake of satnav by the public, from fishing boats and merchant ships, to today’s navigation using nothing but a smartphone with its built-in GPS receiver.

Even so, there is a dark side to GNSS that expands beyond its military usage of guiding cruise missiles and kin to their target. This comes in the form of jamming and spoofing GNSS signals, which can hide illicit activities from monitoring systems and disrupt or disable an enemy’s systems during a war. Along with other forms of electronic warfare (EW), disrupting GNSS signals form a potent weapon that can render the most modern avionics and drone technology useless.

With this in mind, how significant is the threat from GNSS spoofing in particular, and what are the ways that this can be detected or counteracted?

Continue reading “Knowing Your Place: The Implications Of GPS Spoofing And Jamming” →

Things Are Getting Rusty In Kernel Land

May 17, 2022 by Jonathan Bennett 163 Comments

There is gathering momentum around the idea of adding Rust to the Linux kernel. Why exactly is that a big deal, and what does this mean for the rest of us? The Linux kernel has been just C and assembly for its entire lifetime. A big project like the kernel has a great deal of shared tooling around making its languages work, so adding another one is quite an undertaking. There’s also the project culture developed around the language choice. So why exactly are the grey-beards of kernel development even entertaining the idea of adding Rust? To answer in a single line, it’s because C was designed in 1971, to run on the minicomputers at Bell Labs. If you want to shoot yourself in the foot, C will hand you the loaded firearm.

On the other hand, if you want to write a kernel, C is a great language for doing low-level coding. Direct memory access? Yep. Inline assembly? Sure. Runs directly on the metal, with no garbage collection or virtual machines in the way? Absolutely. But all the things that make C great for kernel programming also make C dangerous for kernel programming.

Now I hear your collective keyboards clacking in consternation: “It’s possible to write safe C code!” Yes, yes it is possible. It’s just very easy to mess up, and when you mess up in a kernel, you have security vulnerabilities. There’s also some things that are objectively terrible about C, like undefined behavior. C compilers do their best to do the right thing with cursed code like i++ + i++; or a[i] = i++;. But that’s almost certainly not going to do what you want it to, and even worse, it may sometimes do the right thing.

Rust seems to be gaining popularity. There are some ambitious projects out there, like rewriting coreutils in Rust. Many other standard applications are getting a Rust rewrite. It’s fairly inevitable that the collection of Rust developers started to ask, could we invade the kernel next? This was pitched for a Linux Plumbers Conference, and the mailing list response was cautiously optimistic. If Rust could be added without breaking things, and without losing the very things that makes Rust useful, then yes it would be interesting. Continue reading “Things Are Getting Rusty In Kernel Land” →

NVIDIA Releases Drivers With Openness Flavor

May 13, 2022 by Arya Voronova 27 Comments

This year, we’ve already seen sizeable leaks of NVIDIA source code, and a release of open-source drivers for NVIDIA Tegra. It seems NVIDIA decided to amp it up, and just released open-source GPU kernel modules for Linux. The GitHub link named open-gpu-kernel-modules has people rejoicing, and we are already testing the code out, making memes and speculating about the future. This driver is currently claimed to be experimental, only “production-ready” for datacenter cards – but you can already try it out!

The Driver’s Present State

Of course, there’s nuance. This is new code, and unrelated to the well-known proprietary driver. It will only work on cards starting from RTX 2000 and Quadro RTX series (aka Turing and onward). The good news is that performance is comparable to the closed-source driver, even at this point! A peculiarity of this project – a good portion of features that AMD and Intel drivers implement in Linux kernel are, instead, provided by a binary blob from inside the GPU. This blob runs on the GSP, which is a RISC-V core that’s only available on Turing GPUs and younger – hence the series limitation. Now, every GPU loads a piece of firmware, but this one’s hefty!

Barring that, this driver already provides more coherent integration into the Linux kernel, with massive benefits that will only increase going forward. Not everything’s open yet – NVIDIA’s userspace libraries and OpenGL, Vulkan, OpenCL and CUDA drivers remain closed, for now. Same goes for the old NVIDIA proprietary driver that, I’d guess, would be left to rot – fitting, as “leaving to rot” is what that driver has previously done to generations of old but perfectly usable cards. Continue reading “NVIDIA Releases Drivers With Openness Flavor” →