Keep OSNews alive by becoming a Patreon, by donating through Ko-Fi, or by buying merch!

Monthly Archive:: January 2018

Reading disks from 1988 in 2018

I used an Apple IIe computer throughout high school and into my second year in college, before I bought a Mac SE. That following summer I sold the Apple IIe and everything that came with it - the monitor, floppy drives, and dot-matrix printer - and pocketed the cash. What I was left with were two boxes containing two dozen 5.25-inch floppy disks.

I could've thrown the disks away - I had already transferred all the files I cared about to the Mac. But for some reason I saved them instead. And the two dozen floppy disks stayed in two battered boxes for the next 27 years.

Apple’s iOS security document

Apple designed the iOS platform with security at its core. When we set out to create the best possible mobile platform, we drew from decades of experience to build an entirely new architecture. We thought about the security hazards of the desktop environment, and established a new approach to security in the design of iOS. We developed and incorporated innovative features that tighten mobile security and protect the entire system by default. As a result, iOS is a major leap forward in security for mobile devices.

This document provides details about how security technology and features are implemented within the iOS platform. It will also help organizations combine iOS platform security technology and features with their own policies and procedures to meet their specific security needs.

Some light reading over the weekend.

What really happened with Vista: an insider’s retrospective

I enjoyed reading Terry Crowley's thoughtful blog (What Really Happened with Vista). Terry worked in the Office organization and did a fantastic job covering the complex machinations that went into Windows Vista and the related but doomed Longhorn project - from an outsider's point of view.

He correctly identified many of the problems that dogged the project and I don't mean to rehash any of them here. I figured it was only fair to try to offer an insider's view of the same events. I can't hope to be as eloquent or thorough as Terry but hope to shed some light on what went wrong. Ten years have gone by since the original release date of Windows Vista but the lessons seem more relevant now than ever.

I really enjoy these stories from people involved with the Vista project. Even though we complained left and right about Vista itself, the release was still hugely important and many of Windows NT's core systems were rewritten from scratch, and we still profit from those reworks and rewrites today.

Doesn't retroactively make using Vista any less painful, though.

See the long-lost NES prototype of SimCity

Gamers of a certain age probably remember that Nintendo worked with Maxis to port a version of the seminal SimCity to the brand-new SNES in 1991. What most gamers probably don't realize is that an NES version of the game was developed at the same time and cancelled just before its planned release.

That version of the game was considered lost for decades until two prototype cartridges surfaced in the collecting community last year. One of those prototypes has now been obtained and preserved by the Video Game History Foundation's (VGHF's) Frank Cifaldi, who demonstrated the emulated ROM publicly for the first time at MAGFest last weekend.

I'm a SimCity 2000 person myself, but the original SimCity is a classic, and I love that they finally managed to preserve it.

Apple is moving its Chinese iCloud operations to a local firm

Apple is moving its Chinese iCloud operations from its own datacenters to a local Chinese company run by the government.

The firm is called Guizhou-Cloud Big Data (GCBD). It's based in Guizhou Province and supervised by a board ran by government-owned businesses. In emails to mainland Chinese customers, Apple says that the move enables "us to continue improving the speed and reliability of iCloud and to comply with Chinese regulations."

But there's also the chance that closer ties with the Chinese government might mean more regulation, which Apple has a record of abiding closely to in the past. Last July, Apple deleted VPN apps from the App Store that had helped netizens evade Chinese censorship, "because it includes content that is illegal in China." Those who aren't happy with the move at least have the option of closing their iCloud accounts.

Read into it what you will, but the ties between Apple and the Chinese government are strengthening. One has to wonder how long until Apple has to open up iMessage's encryption.

The fight for patent-unencumbered codecs is nearly won

Apple joining the Alliance for Open Media is a really big deal. Now all the most powerful tech companies - Google, Microsoft, Apple, Mozilla, Facebook, Amazon, Intel, AMD, ARM, Nvidia - plus content providers like Netflix and Hulu are on board. I guess there's still no guarantee Apple products will support AV1, but it would seem pointless for Apple to join AOM if they're not going to use it: apparently AOM membership obliges Apple to provide a royalty-free license to any "essential patents" it holds for AV1 usage.

It seems that the only thing that can stop AOM and AV1 eclipsing patent-encumbered codecs like HEVC is patent-infringement lawsuits (probably from HEVC-associated entities).

I can barely believe this is still a thing, and that it seems like a positive outcome.

Gemini is a tiny Android laptop with the spirit of Psion

The Gemini is a clamshell Android device with an 18:9 ultrawide 1080p screen and a compact but more-or-less full physical keyboard. It runs on a 10-core MediaTek Helio X27 processor and has 4GB of RAM, a 4,220mAh battery, and two USB-C ports. It’s 15.1mm thick when closed and weighs 308g. There are both Wi-Fi-only and LTE-capable models. The software is pretty much stock Android with a useful customized dock that can be brought up anywhere, and you can also dual-boot into Linux for more customization.

This is exactly what I've always wanted. A tiny Psion Series 5-like computer running a modern operating system. This machine can run Android and regular Linux, and seems quite similar in concept to the GPD Pocket 7, which sadly seems to be hard to come by here in The Netherlands (I'd want to run Haiku on the GPD Pocket 7). To be honest, I'm not entirely sure what's I'd use such a tiny laptop for, but they're tiny enough they're not really taking up space.

Performance impact of Spectre, Meltdown patches on Windows

From Microsoft's blog:

Last week the technology industry and many of our customers learned of new vulnerabilities in the hardware chips that power phones, PCs and servers. We (and others in the industry) had learned of this vulnerability under nondisclosure agreement several months ago and immediately began developing engineering mitigations and updating our cloud infrastructure. In this blog, I'll describe the discovered vulnerabilities as clearly as I can, discuss what customers can do to help keep themselves safe, and share what we've learned so far about performance impacts.

The basic gist here is this: the older your processor and the older your Windows version, the bigger the performance impact will be. Windows 10 users will experience a smaller performance impact than Windows 7 and 8 users, and anyone running Haswell or older processors will experience a bigger impact than users of newer processors.

Everything is too complicated

It's the very beginning of CES 2018, and the first trickles of gadget news are starting to come out. The flood begins tomorrow as the show floor opens and keynotes and press conferences begin in earnest. It's easy to see the broad themes of the show and the tech industry at large already forming: smart assistants everywhere, sensors and radios in every device you can think of, and an eternal hope that something, anything, will be the reason people will finally upgrade their TVs.

All of that is exciting - I love gadgets and am one of the few crazy people that think CES is incredibly fun! - but I want to take a half-step back before it all begins and point out something obvious: most people have no idea how any of these things work, and are already hopelessly confused by the tech they have.

Shoving a display and garbage software on every single possible household item is simply a really, really dumb idea. Add networking into the mix, and it becomes outright dangerous. People end up with products they have no idea how to use, that quickly become outdated, aren't getting software updates, and quickly become dangerous attack vectors for all sorts of possible criminals.

The article also touches on something else - namely, that even things like smartphones are getting way, way too complicated for most people. I, too, am continuously surprised by how little people around me really know about their smartphone - be it iOS or Android - and what certain things mean or how certain functions work, or that they even have said functions at all. Tech companies are doing a terrible job of exposing users to functionality in a meaningful, understandable way.

The oldest x86 processor still supported by a modern Linux kernel?

What is the oldest x86 processor that is still supported by a modern Linux kernel in present time?

I asked the above quiz question during the Geekcamp tech conference in Nov 2017 during my emcee role. The theoretical answer as you can glean from the title of this post is the 486 which was first released in 1989. I determined that fact from this article where support for the 386 was dropped in Dec 2012.

To get you interested, here is the result of my effort.

Cool project.

An 8-tube module from a 1954 IBM mainframe examined

IBM's vacuum tube computers of the 1950s were built from pluggable modules, each holding eight tubes and the associated components. I recently came across one of these modules so I studied its circuitry. This particular module implements five contact debouncing circuits, used to clean up input from a key or relay. When you press a key, the metal contacts tend to bounce a bit before closing, so you end up with multiple open/closed signals, rather than a nice, clean signal. The signal needs to be "debounced" to remove the extra transitions before being processed by a computer.

This is so far before my time, it basically looks like 19th century machinery to me. The steps between this module and what we have today blow my mind.

Finding a CPU design bug in the Xbox 360

The recent reveal of Meltdown and Spectre reminded me of the time I found a related design bug in the Xbox 360 CPU - a newly added instruction whose mere existence was dangerous.

Back in 2005 I was the Xbox 360 CPU guy. I lived and breathed that chip. I still have a 30-cm CPU wafer on my wall, and a four-foot poster of the CPU’s layout. I spent so much time understanding how that CPU's pipelines worked that when I was asked to investigate some impossible crashes I was able to intuit how a design bug must be their cause. But first, some background...

Interactive X Linux desktop rendered to TTY and streamed over SSH

I'm travelling around the world and sometimes I don't have very good Internet. If all I have is a 3kbps connection tethered from my phone then it's good to SSH into my server and browse the web through elinks. That way my server downloads the web pages and uses the limited bandwidth of my SSH connection to display the result. But it lacks JS support and all that other modern HTML5 goodness. Texttop is simply a way to have the power of a remote server running a desktop, but interfaced through the simplicity of a terminal and very low bandwidth.

Why not VNC? Well VNC is certainly one solution but it doesn't quite have the same ability to deal with extremely bad Internet. Texttop uses MoSH to further reduce the bandwidth and stability requirements of the connection. Mosh offers features like automatic reconnection of dropped connections and diff-only screen updates. Also, other than SSH or MoSH, Texttop doesn't require a client like VNC. But of course another big reason for Texttop is that it's just very cool geekery.

Xerox Alto zero-day

We've been archiving a bunch of old Xerox Alto disk packs from the 1970s. A few of them turned out to be password-protected, so I needed to figure out how to get around the password protection. I've developed a way to disable password protection, as well as a program to find the password instantly.

Xerox has failed to respond to this severe security hole in their computer, and every day they refuse to patch this vulnerability is a day their customers run a massive risk. Irresponsible.

The T2 chip makes the iMac Pro the start of a Mac revolution

The T2 processor isn't doing the heavy lifting in the iMac Pro - that's the Intel Xeon processor with between 8 and 14 processor cores. The T2 is the brain behind that brain, running the subsystems of the iMac Pro from a single piece of Apple-built silicon. The result is a simplified internal design that doesn’t require multiple components from multiple manufacturers.

On most Macs, there are discrete controllers for audio, system management and disk drives. But the T2 handles all these taks. The T2 is responsible for controlling the iMac Pro's stereo speakers, internal microphones, and dual cooling fans, all by itself.

It's a fascinating chip that certainly puts Apple ahead of its competitors, but at the same time, it's going to make installing non-approved operating systems on Macs ever harder. Sure, they're allowing it for now, but for how long?

Intel claims other chips also affected by design flaw

Update: Google's Project Zero disclosed details about the vulnerability a week ahead of schedule due to growing concerns, and they indeed confirm AMD and ARM processors are also affected:

The Project Zero researcher, Jann Horn, demonstrated that malicious actors could take advantage of speculative execution to read system memory that should have been inaccessible. For example, an unauthorized party may read sensitive information in the system’s memory such as passwords, encryption keys, or sensitive information open in applications. Testing also showed that an attack running on one virtual machine was able to access the physical memory of the host machine, and through that, gain read-access to the memory of a different virtual machine on the same host.

These vulnerabilities affect many CPUs, including those from AMD, ARM, and Intel, as well as the devices and operating systems running them.




Intel just published a PR statement about the processor flaw, and in it, it basically throws AMD and ARM under the bus. According to Intel, reports that only its own processors are affected are inaccurate, namedropping specifically AMD and ARM just to make it very clear who we're talking about here. From the statement:

Recent reports that these exploits are caused by a "bug" or a "flaw" and are unique to Intel products are incorrect. Based on the analysis to date, many types of computing devices - with many different vendors' processors and operating systems - are susceptible to these exploits.

Intel is committed to product and customer security and is working closely with many other technology companies, including AMD, ARM Holdings and several operating system vendors, to develop an industry-wide approach to resolve this issue promptly and constructively. Intel has begun providing software and firmware updates to mitigate these exploits. Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time.

More to surely come.

Intel processor design flaw forces Linux, Windows redesign

A fundamental design flaw in Intel's processor chips has forced a significant redesign of the Linux and Windows kernels to defang the chip-level security bug.

Programmers are scrambling to overhaul the open-source Linux kernel's virtual memory system. Meanwhile, Microsoft is expected to publicly introduce the necessary changes to its Windows operating system in an upcoming Patch Tuesday: these changes were seeded to beta testers running fast-ring Windows Insider builds in November and December.

Crucially, these updates to both Linux and Windows will incur a performance hit on Intel products. The effects are still being benchmarked, however we're looking at a ballpark figure of five to 30 per cent slow down, depending on the task and the processor model. More recent Intel chips have features - such as PCID - to reduce the performance hit.

That's one hell of a bug.

Google Fuchsia for Pixelbook

We've been talking about Google's mysterious Fuchsia operating system for a while now, and today, we have a new piece of the puzzle. It's a small piece, for sure, but with Google being so incredibly secretive about the whole thing, we take what we can get. As it turns out, Google has added support for its Pixelbook to Fuchsia, and added a page on how to prepare the Pixelbook for Fuchsia installation, and you can check the how-to commit for information about the installation itself.

Still a far cry from anything even remotely tangible about where Fuchsia is going, but even a slow drip can eventually fill a bucket.

Arcan 0.5.4, Durden 0.4 released

Ending the year a new release of the "desktop engine" Arcan and its reference desktop environment, Durden.

Arcan is a different take on how to glue the user-experience side of operating systems together. It has been in development for well over a decade, with the modest goals of providing a more secure, faster, safer and flexible alternative to both Xorg and terminal emulators, as well as encouraging research.

The latest release improves on areas such as crash resilience, wayland client support, VR devices, OpenBSD support and visual goodies. You can read through the full release post, with some of the more technical bits in the related articles about crash-resilient Wayland compositing and "AWK" for multimedia.

Amiga 1000 Phoenix motherboard replacement project

First post of the new year - I hope y'all had a good one - and we're talking Amiga.

In October of 2017 I found a really nice accelerator card on Ebay for my stock Amiga 1000 - the Blizzard Turbo Memory Board. My original thought was I would install it into my 1000 and lose the side-car RAM expansions to regain some valuable desk space. Plus - 8MB? That’s gobs for the work I personally do on my Amigas. It was originally designed for the Amiga 500 or 2000 and additionally gave a modest speed boost of 14 Mhz. From my personal experience, 7 Mhz is plenty for the vast majority of Amiga games and software. However in some rare cases 14, 25 or even 40 Mhz can greatly improve the user experience with some math-intensive games and software. This little board seemed the perfect fit for my 1000’s needs.

I then got to talking to the seller on Ebay who was based in Australia. After a short amount of time I came to learn that he had in his possession an ultra-rare Phoenix board, too. Within a few days, money was exchanged and the Phoenix began its long journey from Australia to Seattle, Washington.

This is one of those stories where you just sit back, grab a warm drink, and just enjoy.