With the recent launch of Windows 11 Microsoft also made having a hardware TPM module mandatory. Although this technology is not new (it was introduced in Windows 10 and Windows Server 2016), now, that most people can’t upgrade to Windows 11, it will (slowly) become mainstream. (My personal opinion on it is that is probably a step in the right direction, but Microsoft could have handled mandating it better..) Several months ago, when I heard about this new requirement, I checked how much this upgrade for me would cost. At the time prices for a TPM2.0 module for my motherboard (Gigabyte AORUS GAMING 3) started at around €150, which is not much less then, but definitely comparable with, the price of the motherboard itself. Not prepared to pay that much for a “free” Windows 11 upgrade, I started to look into if and how I could create the same thing on my own. A cool and actually useful project – and the required code and schematics are available on GitHub.
This is approximately as wise as taking off from Mars in a ragtop rocket, but don’t worry, the math all checks out. My theory is that compiling less code will be faster than compiling more code, but first we must find the code so we know not to compile it. This is vital information to know in your day-to-day computing life.
We are excited to announce the availability of VSI OpenVMS E9.2 for x86-64, field test version of the upcoming V9.2 release. This is the next step in the journey to migrate OpenVMS to the x86-64 platform. The E9.2 release allows you to use the operating system with some of the most commonly-used hypervisors and includes a host of newly migrated applications. VSI has been porting OpenVMS to x86-64 for a while now, and it seems they’re getting quite close to general availability. E9.2 is focused on x86 hypervisors, and the porting effort as a whole should provide a future upgrade path for VMS users for a long time to come.
Android’s Accessibility API is an incredibly powerful tool intended for developers to build apps for users with disabilities. The API lets apps read the contents of the screen and perform inputs on behalf of the user, which are essential functions for screen readers and alternative input systems. Unfortunately, these functions are also incredibly useful for malicious apps that want to steal data from users, which is why Google has been cracking down on which apps are allowed to use the Accessibility API. Google has already limited which apps on Google Play can use the Accessibility API, and in Android 13, they’re taking things one step further by heavily restricting API access for apps that the user has sideloaded from outside of an app store. And so, step by step, Google locks down more and more of Android. Some of the most fascinating and unique applications use the Accessiblity APIs, and making it harder for them to do their thing will have a chilling effect on the wild innovation we see in the Android world. For now, this restriction only applies to applications sideloaded outside of application stores (e.g, applications installed through F-Droid are not affected), but I have my doubt slippery slope is suddenly going to even out at this specific point. After all, we must be protected against ourselves at all costs.
In a joint effort, tech giants Apple, Google, and Microsoft announced Thursday morning that they have committed to building support for passwordless sign-in across all of the mobile, desktop, and browser platforms that they control in the coming year. Effectively, this means that passwordless authentication will come to all major device platforms in the not too distant future: Android and iOS mobile operating systems; Chrome, Edge, and Safari browsers; and the Windows and macOS desktop environments. A passwordless login process will let users choose their phones as the main authentication device for apps, websites, and other digital services, as Google detailed in a blog post published Thursday. Unlocking the phone with whatever is set as the default action — entering a PIN, drawing a pattern, or using fingerprint unlock — will then be enough to sign in to web services without the need to ever enter a password, made possible through the use of a unique cryptographic token called a passkey that is shared between the phone and the website. Passwords are a terrible security practice, and while password managers make the whole ordeal slightly less frustrating, using my phone’s fingerprint reader to log into stuff seems like a very welcome improvement.
Ars Technica writes: Back in 1995, the Microsoft Kids division of the company released a program called Microsoft 3D Movie Maker. The same year that the original Toy Story proved that feature-length 3D computer animation was feasible, people could install software on their home computers that could spit out crude-but-creative 3D animated movies at 6 to 8 frames per second. Aside from releasing Doraemon and Nickelodeon-specific versions of Movie Maker later on, Microsoft never really returned to this software… until now. Microsoft Developer Division Community Manager Scott Hanselman announced yesterday that Microsoft was open-sourcing the code for 3D Movie Maker, posting it to Github in a read-only repository under an MIT license. Microsoft made some seriously weird products back in the ’90s, and this is definitely one of them. It’s great to see things like this released as open source – these are not the products that set the world on fire, but the idea to get it to compile and run on modern systems will surely spark the imagination of quite a few developers.
Sculpt OS version 22.04 introduces the concept of service-level sandboxing and features completely new drivers for wireless, graphics, and USB. On the user-visible surface, the new version of Sculpt OS looks and feels familiar to users of the previous version. Under the hood, however, at the nitty-gritty hardware-support level, it features completely revamped device drivers for Intel wireless, Intel graphics, and USB. Get Sculpt OS’ latest release from the download page, and be sure to read the documentation for more detailed information.
The Trinity Desktop Environment, a fork of the KDE 3.x codebase, has released its latest version. This release comes with a new D-Bus based polkit authentication agent, new markdown document viewer, support for HTML5 in Quanta, support for Let’s Encrypt certificates, some improvements to GUI options, better cooperation between tdm and plymouth, fix for ICEAuthority ownership stealing when using sudo, various other bug fixes and improvements. It also adds support for Ubuntu Jammy while it drops support for Debian Jessie and Ubuntu Trusty. C++11 is now allowed in the code base. I doubt the audience for a KDE 3.x desktop is massive, but thanks to the wonders of open source – the people that want it, can have it.
Unity 7.6 will be the first major release of Unity in 6 years (the last release was in May 2016). We have restarted the active development of Unity7 and will be releasing new versions with more features regularly. I was never a fan of Ubuntu’s Unity, but I’ve seen quite a few people over the years who miss it. Your call has been answered – this first release has a a lot of visual touch-ups and updates to make it look a bit more modern, and there’s bugfixes in here, too, of course.
A lot has changed since release 0.6.0! First thing, it is impossible to collect all the changes that happened since December 24, 2020 into one set of release notes, so this will focus on the highlights. It was very important to me that this be a release targeting the foundations of Redox OS. This includes, the bootloader, the filesystem, the package manager, the kernel, the drivers, and much more. The focus was on enabling Redox OS to boot on the widest set of hardware possible. Redox is a Rust-based operating system with a microkernel and a UNIX-like paradigm and an optional GUI. Its lead developer works for System76 as principal engineer.
It’s already April and we’ve been making steady progress refining the features and stability of Android 13, building around our core themes of privacy and security, developer productivity, as well as tablet and large screen support. Today we’re moving into the next phase of our cycle and releasing the first Beta of Android 13. Android 13 development seems to be ahead of the regular schedule.
Today, we’re releasing the first developer preview for the Privacy Sandbox on Android, which provides an early look at the SDK Runtime and Topics API. You’ll be able to do preliminary testing of these new technologies and evaluate how you might adopt them for your solutions. This is a preview, so some features may not be implemented just yet, and functionality is subject to change. See the release notes for more details on what’s included in the release. We’ll see if this initiative will have a material impact on user privacy on Android, but I have my sincerest doubt. Even if does make more applications respect your privacy, I have a feeling this is going to be a classic situation of “rules for thee but not for me” (a phrase far newer and more recent than I realised).
Well color me old! The ZX Spectrum (affectionately known as “Speccy” or just “Spectrum” by its fans), one of the best-selling microcomputers of all time, was released 40 years ago today. Can you believe it still has a large and active community creating new content, archiving old content, and hacking on all sorts of hardware? I have never owned or used one, but the Spectrum is one of those machines everyone is familiar with – like the C64, the Apple II, TRS 80, and so on.
Apple today launched the Self Service Repair Store, allowing iPhone customers in the United States access to parts and manual that they can use to repair their own devices. The new store enables repairs of iPhone SE, iPhone 12 and iPhone 13 components, including display, battery and camera replacements. Apple also said it will launch Mac self-service repairs later this year. A good start.
Microsoft’s upgrade to Windows 11 is largely considered the smoothest we’ve ever had. The Microsoft Digital Employee Experience team was able to upgrade 190,000 employee devices in just five weeks. We learned a lot so, in this post, I’m sharing our learnings with you to help with your deployment journey. Our success was built around several factors: far fewer app compatibility challenges than in the past, not needing to build out a plethora of disk images, and delivery processes and tools already that were greatly improved during the rollout of Windows 10. We divided our upgrade into three stages: plan, prepare, and deploy. It would be pretty pathetic if not even Microsoft itself could smoothly update its employees’ machines to the latest version of Windows, but that being said – I do not envy the people tasked with doing so.
CPUs in Apple Silicon chips are different, as they contain two different core types, one designed for high performance (Performance, P or Firestorm cores), the other for energy efficiency (Efficiency, E or Icestorm cores). For these to work well, threads need to be allocated by core type, a task which can be left to apps and processes, as it is in Asahi Linux, or managed by the operating system, as it is in macOS. This article explains how macOS manages core allocation in all Apple’s M1 series chips, in what it terms asymmetric multiprocessing (AMP, although others prefer to call this heterogeneous computing). This design has now also made its way to x86 with Intel’s 12th Gen processors.
Twitter, Inc. today announced that it has entered into a definitive agreement to be acquired by an entity wholly owned by Elon Musk, for $54.20 per share in cash in a transaction valued at approximately $44 billion. Upon completion of the transaction, Twitter will become a privately held company. Elon Musk is now the founder and inventor of Twitter.
Ubuntu 22.04 LTS comes with the latest GNOME 42 desktop environment with the triple buffering patch included, yet it still uses apps from the GNOME 41 stack due to compatibility issues between GTK4 apps included in the upstream release and Ubuntu’s Yaru theme. Apps that weren’t ported to GTK4 are from the GNOME 42 stack, such as the Nautilus (Files) file manager. This is also the first LTS release with Wayland as its default (except for machines with NVIDIA GPUs, which will stick with X.org), which is a major milestone. On top of that, it comes with the latest releases of all the various packages that make up a Linux system, and will serve as the base for countless popular Ubuntu-based distributions. Of course, the countless other Ubuntu flavours also made the jump to 22.04.
OpenBSD 7.1 has been released. The biggest improvement in this point release is support for Apple Silicon, which is now ready for general use. Of course, there’s a lot more in this new release, so head on over to the changelog to get all the details.
QEMU 7.0 is out today as the newest version of this important piece of the open-source Linux virtualization stack. Since QEMU 6.2 at the end of last year, developers at Red Hat and other organizations have been busy working on QEMU 7.0 as this open-source emulator widely used as part of the free software Linux virtualization stack. QEMU 7.0 brings support for Intel AMX, a lot of ongoing RISC-V work, and more. QEMU is one of the great success stories of open source – and one operating system and classic computing enthusiasts benefit from every day.