The Intel 386 SX CPU quickly replaced the 286 CPU in the early 1990s. For a time, it was a very popular CPU, especially for people who were wanting to run Microsoft Windows. Yet the two CPUs run at nearly identical speed. So what was the big deal? The 286 vs 386SX argument could be confusing in 1991, and it’s not much clearer today. Here at OSNews we pride ourselves in pointing you to the most relevant, up-to-date buying advice available on the internet.
Earlier this month, Apple unveiled a system that would scan iPhone and iPad photos for child sexual abuse material (CSAM). The announcement sparked a civil liberties firestorm, and Apple’s own employees have been expressing alarm. The company insists reservations about the system are rooted in “misunderstandings.” We disagree. We wrote the only peer-reviewed publication on how to build a system like Apple’s — and we concluded the technology was dangerous. We’re not concerned because we misunderstand how Apple’s system works. The problem is, we understand exactly how it works. There’s now so much evidence from credible, trustworthy people and organisations that Apple’s system is bad and dangerous, that I find it hard to believe there are still people cheering Apple on.
I at least peruse if not review in depth the vast majority of all those PRs, and every time I see a PR that is likely to impact performance, I make a note of it in a running log, giving me a long list of improvements I can revisit when it’s blog time. That made this August a little daunting, as I sat down to write this post and was faced with the list I’d curated of almost 550 PRs. Don’t worry, I don’t cover all of them here, but grab a large mug of your favorite hot beverage, and settle in: this post takes a rip-roarin’ tour through ~400 PRs that, all together, significantly improve .NET performance for .NET 6. You might want to get some coffee.
The theme for this release has been adding new functionality to the MATE Desktop while maintaining the look and feel that we all know and love. While all the added features are surely quite exciting we also did not forget to do tons of bugfixing, modernising the code base and optimizing the performance. MATE is one of the two great alternatives for people who find GNOME 3 and later unpleasant (the other being Cinnamon, my DE of choice).
In Windows 11, Microsoft has changed the way you set default apps. Like Windows 10, there’s a prompt that appears when you install a new browser and open a web link for the first time. It’s the only opportunity to easily switch browsers, though. Unless you tick “always use this app,” the default will never be changed. It’s incredibly easy to forget to toggle the “always use this app” option, and simply launch the browser you want from this prompt and never see this default choice again when you click web links. Microsoft has changed the way default apps are assigned in Windows 11, which means you now have to set defaults by file or link type instead of a single switch. In the case of Chrome, that means changing the default file type for HTM, HTML, PDF, SHTML, SVG, WEBP, XHT, XHTML, FTP, HTTP, and HTTPS. That’s what you get when you use proprietary operating systems. Windows and macOS are not designed for you; they’re designed for Microsoft and Apple, respectively.
Researchers have produced a collision in iOS’s built-in hash function, raising new concerns about the integrity of Apple’s CSAM-scanning system. The flaw affects the hashing system, called NeuralHash, which allows Apple to check for exact matches of known child-abuse imagery without possessing any of the images or gleaning any information about non-matching pictures. On Tuesday, a GitHub user called Asuhariet Ygvar posted code for a reconstructed Python version of NeuralHash, which he claimed to have reverse-engineered from previous versions of iOS. The GitHub post also includes instructions on how to extract the NeuralMatch files from a current macOS or iOS build. Once the code was public, more significant attacks were quickly discovered. A user called Cory Cornelius produced a collision in the algorithm: two images that generate the same hash. If the findings hold up, it will be a significant failure in the cryptography underlying Apple’s new system. American tech media and bloggers have been shoving the valid concerns aside ever since Apple announced this new backdoor into iOS, and it’s barely been a week and we already see major tentpoles come crashing down. I try not to swear on OSNews, but there’s no other way to describe this than as a giant clusterfuck of epic proportions.
Speaking of Debian, there’s even bigger news than a new Debian GNU/Hurd release – Debian 11.0 is out and about! This release contains over 11,294 new packages for a total count of 59,551 packages, along with a significant reduction of over 9,519 packages which were marked as obsolete and removed. 42,821 packages were updated and 5,434 packages remained unchanged. As always, Debian release are big, and they are hugely important as they serve as the base for some of the most popular Linux distributions out there.
It is with huge pleasure that the Debian GNU/Hurd team announces the release of Debian GNU/Hurd 2021. This is a snapshot of Debian “sid” at the time of the stable Debian “bullseye” release (August 2021), so it is mostly based on the same sources. It is not an official Debian release, but it is an official Debian GNU/Hurd port release. In this release, the port of go has been completed, experimental support for APIC, SMP, and 64bit has been added, and more.
A great intro to a classic platform by way of emulation and optionally even adapting a real physical keyboard: Back in the late 80s and through the 90s, Unix workstations were super powerful, super cool, and super expensive. If you were making 3D graphics or developing applications, you wanted a high-performance workstation and Sun made some of the best ones. But unless you worked for a huge company, university, or government, they were probably too expensive. More than twenty years later, we have much more powerful and affordable computers, so let’s emulate the old systems and see what it was like to run some of the coolest computers you could buy in the 90s. This is another in the series from the same author as the recently linked virtual NeXT machine, that also includes an entry for a virtual BeBox to experience BeOS.
This is the Commodore 64 KERNAL, modified to run on the Atari 8-bit line of computers. They’re practically the same machine; why didn’t someone try this 30 years ago? No time like the present.
Apple employees have flooded an Apple internal Slack channel with more than 800 messages on the plan announced a week ago, workers who asked not to be identified told Reuters. Many expressed worries that the feature could be exploited by repressive governments looking to find other material for censorship or arrests, according to workers who saw the days-long thread. Past security changes at Apple have also prompted concern among employees, but the volume and duration of the new debate is surprising, the workers said. Some posters worried that Apple is damaging its leading reputation for protecting privacy. It’s a complete 180 from Apple’s behaviour and statements (in western markets) – of course employees are going to be worried. I’ve been warning for years that Apple’s position on privacy was nothing more than a marketing ploy, and now Apple employees, too, get a taste of their own medicine that they’ve been selling in China and various other totalitarian regimes.
Hello Windows Insiders! Today we are rolling out the first set of updates for several apps that come included as part of Windows 11. The following app updates are rolling out to Windows Insiders in the Dev Channel at first. Microsoft has updated some of the default Windows applications – Snipping Tool, Calculator, and Mail & Calendar.
Their legislation would bar the companies from certain conduct that would tend to force developers to use their app stores or payment systems. It also would obligate the companies to protect app developers’ rights to tell consumers about lower prices and offer competitive pricing. It would effectively allow apps to be loaded onto Apple users’ devices outside of the company’s official app store. There’s so much movement on this front, I highly doubt Apple and Google will be able to stop it. This is one of the very, very rare cases where both sides of the political spectrum seem to somewhat agree, and I hope they can make it stick. It’s definitely not enough, but it’s a step in the right direction. I’m an extremist – all source code should be freely available (not necessarily open source – just viewable), to give consumers and society as a whole the ability to ensure they’re not being spied on, lied to, or endangered by foreign entities or corporate trickery. If copyright is good enough for writers, artists, and musicians, it’s damn well good enough for programmers. With how vital computers and software have become – woven into the fabric of our society – we as people should be able to see and check what those threads are doing and where they’re going to and coming from. Corporations have shown time and time again that they are not trustworthy entities and that they do not have society’s best interests at heart, and we need tools to bring the balance of power back – black boxes of code are dangerous.
So imagine my surprise when I dug around in a quarter-century-old archive to find a .zip file containing something that purported to be the original executable of Labyrinth. Surely such an ancient piece of code – written for Windows 3.1 – wouldn’t launch? Well, after a bit of fiddling with the Windows compatibility settings, I was shocked – and extremely pleased – to see that, yes, it most certainly did. It shouldn’t be surprising that a piece of good Windows code from 30 years ago still runs on Windows 10 today, and yet, it always is.
An operating system I’ve been writing since ~June 2017. Although it’s a long shot (and very optimistic), I ultimately intend it to replace Linux and Windows as a desktop operating system. Very optimistic, but there’s quite a few things here already. The code is on gitlab, where you can find more information, too.
MorphOS 3.15 ram-handler contains a bug that when unlucky may results in the RAM: root directory to appear to contain many duplicate entries. Multiple users had reported this over the years, but until recently the root cause of this issue had eluded us. Due to recent developments, the bug has finally been located and fixed (thanks to AngryTom for help!). Fixed ram-handler will be released as the part of the future MorphOS 3.16 release. Meanwhile you can install the following patch that fixes the problem for MorphOS 3.15. I know this isn’t a major new release or anything, but it’s rather rare and interesting to see a small, standalone update like this being release for a small, alternative operating system. Usually, these get rolled into major new releases or nightlies, so I found this interesting.
In 1985 Steve Jobs resigned from Apple and founded NeXT Inc. in order to build the NeXT Computer. It was ahead of its time and had amazing features thanks to the NeXTSTEP operating system, most famously used at CERN by Sir Tim Berners-Lee to create the World Wide Web. NeXTSTEP later became OPENSTEP and when Apple acquired NeXT in 1997, they used it as the basis for Mac OS X and iOS. If you’ve done any Mac or iOS programming, you’ve seen the echoes of NeXTSTEP in the type names – NSObject, NSString, NSDictionary, and many others all come directly from NeXT (NS = NeXTSTEP). These computers cost about as much as a new car when they first came out, so they were out of reach for most people. What was it like to use a top of the line system in the early 90s? Let’s build our own and find out! Exactly as it says on the tin. A fun few hours.
Valve’s “Steam Deck” handheld PC has caused quite a stir among PC gaming geeks, but the biggest shakeup might not be its Nintendo Switch-like form factor. The software running inside of it is the real surprise. Why does the Steam Deck run Linux? Blame Windows. The Steam Deck and the software inside of it are the culmination of a nearly decade-long “hedging strategy” embarked upon by Valve chief Gabe Newell and company many moons ago, when Microsoft tried exerting more control over developers with Windows 8. But it’s also the next phase of Valve’s escape plan. Also, Windows is simply a terrible choice for the Steam Deck. The base model only has 64GB of storage, and Windows 10 will easily take up two-thirds of that.
Dr. Neal Krawetz, one of the leading experts in the area of computer forensics research, digital photo analysis, and related topics, has penned a blog post in which he takes apart Apple’s recent announcement and the technology behind it. He actually has a lot of experience with the very problem Apple is trying to deal with, since he is the creator of FotoForensics, and files CSAM reports to the National Center for Missing and Exploited Children (NCMEC) every day. In fact, he files more reports than Apple, and knows all the ins and outs of all the technologies involved – including reverse-engineering Microsoft’s PhotoDNA, the perceptual hash algorithm NCMEC and Apple are using. The reason he had to reverse-engineer PhotoDNA is that NCMEC refused to countersign the NDA’s they wanted Krawetz to sign, eventually not responding to his requests altogether. Krawetz is one of the more prolific reporters of CSAM material (number 40 out of 168 in total in 2020). According to him, PhotoDNA is not as sophisticated as Apple’s and Microsoft’s documentation and claims make it out to be. Perhaps there is a reason that they don’t want really technical people looking at PhotoDNA. Microsoft says that the “PhotoDNA hash is not reversible”. That’s not true. PhotoDNA hashes can be projected into a 26×26 grayscale image that is only a little blurry. 26×26 is larger than most desktop icons; it’s enough detail to recognize people and objects. Reversing a PhotoDNA hash is no more complicated than solving a 26×26 Sudoku puzzle; a task well-suited for computers. The other major component of Apple’s system, an AI perceptual hash called a NeuralHash, is problematic too. The experts Apple cites have zero background in privacy or law, and while Apple’s whitepaper is “overly technical”, it “doesn’t give enough information for someone to confirm the implementation”. Furthermore, Krawetz “calls bullshit” on Apple’s claim that there is a 1 in 1 trillion error rate. After a detailed analysis of the numbers involved, he concludes: What is the real error rate? We don’t know. Apple doesn’t seem to know. And since they don’t know, they appear to have just thrown out a really big number. As far as I can tell, Apple’s claim of “1 in 1 trillion” is a baseless estimate. In this regard, Apple has provided misleading support for their algorithm and misleading accuracy rates. Krawetz also takes aim at the step where Apple manually reviews possible CP material by sending them from the device in question to Apple itself. After discussing this with his attorney, he concludes: The laws related to CSAM are very explicit. 18 U.S. Code § 2252 states that knowingly transferring CSAM material is a felony. (The only exception, in 2258A, is when it is reported to NCMEC.) In this case, Apple has a very strong reason to believe they are transferring CSAM material, and they are sending it to Apple — not NCMEC. It does not matter that Apple will then check it and forward it to NCMEC. 18 U.S.C. § 2258A is specific: the data can only be sent to NCMEC. (With 2258A, it is illegal for a service provider to turn over CP photos to the police or the FBI; you can only send it to NCMEC. Then NCMEC will contact the police or FBI.) What Apple has detailed is the intentional distribution (to Apple), collection (at Apple), and access (viewing at Apple) of material that they strongly have reason to believe is CSAM. As it was explained to me by my attorney, that is a felony. This whole thing looks, feels, and smells like a terribly designed system that is not only prone to errors, but also easily exploitable by people and governments with bad intentions. It also seems to be highly illegal, making one wonder why Apple were to put this out in the first place. Krawetz hints at why Apple is building this system earlier in this article: Apple’s devices rename pictures in a way that is very distinct. (Filename ballistics spots it really well.) Based on the number of reports that I’ve submitted to NCMEC, where the image appears to have touched Apple’s devices or services, I think that Apple has a very large CP/CSAM problem. I think this might be the real reason Apple is building this system.
Every good operating system needs a web browser, especially as more and more apps move to the web. To that end, Google is preparing to bring the full Google Chrome browser experience to Fuchsia OS. This was inevitable, of course. As the article notes, Fuchsia already has the Chrome engine to display web content if needed, and now they are bringing the whole actual browser over as well. Just another step in the long journey to replace the underpinnings of Android and Chrome OS.
Guest post by